Template modification based on deviation from compliant execution of the template

ABSTRACT

A computationally implemented method includes, but is not limited to: determining whether a plurality of end users deviated from compliantly executing a template designed to facilitate the plurality of end users in achieving one or more target outcomes when one or more emulatable aspects included in the template are emulated by the plurality of end users, the one or more emulatable aspects being based on one or more relevant reported aspects of one or more source users that were deemed to have been relevant to achieving the one or more target outcomes; and modifying the template based, at least in part, on determining that the plurality of end users deviated from compliantly executing the template In addition to the foregoing, other method aspects are described in the claims, drawings, and text forming a part of the present disclosure.

CROSS-REFERENCE TO RELATED APPLICATIONS

The present application is related to and claims the benefit of theearliest available effective filing date(s) from the following listedapplication(s) (the “Related Applications”) (e.g., claims earliestavailable priority dates for other than provisional patent applicationsor claims benefits under 35 USC §119(e) for provisional patentapplications, for any and all parent, grandparent, great-grandparent,etc. applications of the Related Application(s)). All subject matter ofthe Related Applications and of any and all parent, grandparent,great-grandparent, etc. applications of the Related Applications isincorporated herein by reference to the extent such subject matter isnot inconsistent herewith.

RELATED APPLICATIONS

For purposes of the USPTO extra-statutory requirements, the presentapplication constitutes a continuation-in-part of U.S. patentapplication Ser. No. 12/584,489, entitled PERSONALIZED PLAN DEVELOPMENT,naming Shawn P. Firminger; Jason Garms; Roderick A. Hyde; Edward K. Y.Jung; Chris D. Karkanias; Eric C. Leuthardt; Royce A. Levien; Richard T.Lord; Robert W. Lord; Mark A. Malamud; John D. Rinaldo, Jr.; Clarence T.Tegreene; Kristin M. Tolle; Lowell L. Wood, Jr. as inventors, filed 3Sep. 2009, which is currently co-pending, or is an application of whicha currently co-pending application is entitled to the benefit of thefiling date.

For purposes of the USPTO extra-statutory requirements, the presentapplication constitutes a continuation-in-part of U.S. patentapplication Ser. No. 12/584,653, entitled PERSONALIZED PLAN DEVELOPMENT,naming Shawn P. Firminger; Jason Garms; Roderick A. Hyde; Edward K. Y.Jung; Chris D. Karkanias; Eric C. Leuthardt; Royce A. Levien; Richard T.Lord; Robert W. Lord; Mark A. Malamud; John D. Rinaldo, Jr.; Clarence T.Tegreene; Kristin M. Tolle; Lowell L. Wood, Jr. as inventors, filed 8Sep. 2009, which is currently co-pending, or is an application of whicha currently co-pending application is entitled to the benefit of thefiling date.

For purposes of the USPTO extra-statutory requirements, the presentapplication constitutes a continuation-in-part of U.S. patentapplication Ser. No. 12/587,018, entitled PERSONALIZED PLAN DEVELOPMENTBASED ON OUTCOME IDENTIFICATION, naming Shawn P. Firminger; Jason Garms;Roderick A. Hyde; Edward K. Y. Jung; Chris D. Karkanias; Eric C.Leuthardt; Royce A. Levien; Richard T. Lord; Robert W. Lord; Mark A.Malamud; John D. Rinaldo, Jr.; Clarence T. Tegreene; Kristin M. Tolle;Lowell L. Wood, Jr. as inventors, filed 29 Sep. 2009, which is currentlyco-pending, or is an application of which a currently co-pendingapplication is entitled to the benefit of the filing date.

For purposes of the USPTO extra-statutory requirements, the presentapplication constitutes a continuation-in-part of U.S. patentapplication Ser. No. 12/587,127, entitled PERSONALIZED PLAN DEVELOPMENTBASED ON OUTCOME IDENTIFICATION, naming Shawn P. Firminger; Jason Garms;Roderick A. Hyde; Edward K. Y. Jung; Chris D. Karkanias; Eric C.Leuthardt; Royce A. Levien; Richard T. Lord; Robert W. Lord; Mark A.Malamud; John D. Rinaldo, Jr.; Clarence T. Tegreene; Kristin M. Tolle;Lowell L. Wood, Jr. as inventors, filed 30 Sep. 2009, which is currentlyco-pending, or is an application of which a currently co-pendingapplication is entitled to the benefit of the filing date.

For purposes of the USPTO extra-statutory requirements, the presentapplication constitutes a continuation-in-part of U.S. patentapplication Ser. No. 12/590,027, entitled PERSONALIZED PLAN DEVELOPMENTBASED ON ONE OR MORE REPORTED ASPECTS' ASSOCIATION WITH ONE OR MORESOURCE USERS, naming Shawn P. Firminger; Jason Garms; Roderick A. Hyde;Edward K. Y. Jung; Chris D. Karkanias; Eric C. Leuthardt; Royce A.Levien; Richard T. Lord; Robert W. Lord; Mark A. Malamud; John D.Rinaldo, Jr.; Clarence T. Tegreene; Kristin M. Tolle; Lowell L. Wood,Jr. as inventors, filed 29 Oct. 2009, which is currently co-pending, oris an application of which a currently co-pending application isentitled to the benefit of the filing date.

For purposes of the USPTO extra-statutory requirements, the presentapplication constitutes a continuation-in-part of U.S. patentapplication Ser. No. 12/590,039, entitled PERSONALIZED PLAN DEVELOPMENTBASED ON ONE OR MORE REPORTED ASPECTS' ASSOCIATION WITH ONE OR MORESOURCE USERS, naming Shawn P. Firminger; Jason Garms; Roderick A. Hyde;Edward K. Y. Jung; Chris D. Karkanias; Eric C. Leuthardt; Royce A.Levien; Richard T. Lord; Robert W. Lord; Mark A. Malamud; John D.Rinaldo, Jr.; Clarence T. Tegreene; Kristin M. Tolle; Lowell L. Wood,Jr. as inventors, filed 30 Oct. 2009, which is currently co-pending, oris an application of which a currently co-pending application isentitled to the benefit of the filing date.

For purposes of the USPTO extra-statutory requirements, the presentapplication constitutes a continuation-in-part of U.S. patentapplication Ser. No. 12/590,600, entitled PERSONALIZED PLAN DEVELOPMENTBASED ON IDENTIFICATION OF ONE OR MORE RELEVANT REPORTED ASPECTS, namingShawn P. Firminger; Jason Garms; Roderick A. Hyde; Edward K. Y. Jung;Chris D. Karkanias; Eric C. Leuthardt; Royce A. Levien; Richard T. Lord;Robert W. Lord; Mark A. Malamud; John D. Rinaldo, Jr.; Clarence T.Tegreene; Kristin M. Tolle; Lowell L. Wood, Jr. as inventors, filed 10Nov. 2009, which is currently co-pending, or is an application of whicha currently co-pending application is entitled to the benefit of thefiling date.

For purposes of the USPTO extra-statutory requirements, the presentapplication constitutes a continuation-in-part of U.S. patentapplication Ser. No. 12/590,841, entitled PERSONALIZED PLAN DEVELOPMENTBASED ON IDENTIFICATION OF ONE OR MORE RELEVANT REPORTED ASPECTS, namingShawn P. Firminger; Jason Garms; Roderick A. Hyde; Edward K. Y. Jung;Chris D. Karkanias; Eric C. Leuthardt; Royce A. Levien; Richard T. Lord;Robert W. Lord; Mark A. Malamud; John D. Rinaldo, Jr.; Clarence T.Tegreene; Kristin M. Tolle; Lowell L. Wood, Jr. as inventors, filed 12Nov. 2009, which is currently co-pending, or is an application of whicha currently co-pending application is entitled to the benefit of thefiling date.

For purposes of the USPTO extra-statutory requirements, the presentapplication constitutes a continuation-in-part of U.S. patentapplication Ser. No. 12/592,075, entitled DEVELOPMENT OF PERSONALIZEDPLANS BASED ON ACQUISITION OF RELEVANT REPORTED ASPECTS, naming Shawn P.Firminger; Jason Garms; Roderick A. Hyde; Edward K. Y. Jung; Chris D.Karkanias; Eric C. Leuthardt; Royce A. Levien; Richard T. Lord; RobertW. Lord; Mark A. Malamud; John D. Rinaldo, Jr.; Clarence T. Tegreene;Kristin M. Tolle; Lowell L. Wood, Jr. as inventors, filed 17 Nov. 2009,which is currently co-pending, or is an application of which a currentlyco-pending application is entitled to the benefit of the filing date.

For purposes of the USPTO extra-statutory requirements, the presentapplication constitutes a continuation-in-part of U.S. patentapplication Ser. No. 12/592,161, entitled DEVELOPMENT OF PERSONALIZEDPLANS BASED ON ACQUISITION OF RELEVANT REPORTED ASPECTS, naming Shawn P.Firminger; Jason Garms; Roderick A. Hyde; Edward K. Y. Jung; Chris D.Karkanias; Eric C. Leuthardt; Royce A. Levien; Richard T. Lord; RobertW. Lord; Mark A. Malamud; John D. Rinaldo, Jr.; Clarence T. Tegreene;Kristin M. Tolle; Lowell L. Wood, Jr. as inventors, filed 18 Nov. 2009,which is currently co-pending, or is an application of which a currentlyco-pending application is entitled to the benefit of the filing date.

For purposes of the USPTO extra-statutory requirements, the presentapplication constitutes a continuation-in-part of U.S. patentapplication Ser. No. 12/592,544, entitled IDENTIFICATION AND PROVISIONOF REPORTED ASPECTS THAT ARE RELEVANT WITH RESPECT TO ACHIEVEMENT OFTARGET OUTCOMES, naming Shawn P. Firminger; Jason Garms; Roderick A.Hyde; Edward K. Y. Jung; Chris D. Karkanias; Eric C. Leuthardt; Royce A.Levien; Richard T. Lord; Robert W. Lord; Mark A. Malamud; John D.Rinaldo, Jr.; Clarence T. Tegreene; Kristin M. Tolle; Lowell L. Wood,Jr. as inventors, filed 24 Nov. 2009, which is currently co-pending, oris an application of which a currently co-pending application isentitled to the benefit of the filing date.

For purposes of the USPTO extra-statutory requirements, the presentapplication constitutes a continuation-in-part of U.S. patentapplication Ser. No. 12/592,548, entitled IDENTIFICATION AND PROVISIONOF REPORTED ASPECTS THAT ARE RELEVANT WITH RESPECT TO ACHIEVEMENT OFTARGET OUTCOMES, naming Shawn P. Firminger; Jason Garms; Roderick A.Hyde; Edward K. Y. Jung; Chris D. Karkanias; Eric C. Leuthardt; Royce A.Levien; Richard T. Lord; Robert W. Lord; Mark A. Malamud; John D.Rinaldo, Jr.; Clarence T. Tegreene; Kristin M. Tolle; Lowell L. Wood,Jr. as inventors, filed 25 Nov. 2009, which is currently co-pending, oris an application of which a currently co-pending application isentitled to the benefit of the filing date.

For purposes of the USPTO extra-statutory requirements, the presentapplication constitutes a continuation-in-part of U.S. patentapplication Ser. No. 12/592,944, entitled TEMPLATE DEVELOPMENT BASED ONSENSOR ORIGINATED REPORTED ASPECTS, naming Shawn P. Firminger; JasonGarms; Roderick A. Hyde; Edward K. Y. Jung; Chris D. Karkanias; Eric C.Leuthardt; Royce A. Levien; Richard T. Lord; Robert W. Lord; Mark A.Malamud; John D. Rinaldo, Jr.; Clarence T. Tegreene; Kristin M. Tolle;Lowell L. Wood, Jr. as inventors, filed 3 Dec. 2009, which is currentlyco-pending, or is an application of which a currently co-pendingapplication is entitled to the benefit of the filing date.

For purposes of the USPTO extra-statutory requirements, the presentapplication constitutes a continuation-in-part of U.S. patentapplication Ser. No. 12/592,946, entitled TEMPLATE DEVELOPMENT BASED ONSENSOR ORIGINATED REPORTED ASPECTS, naming Shawn P. Firminger; JasonGarms; Roderick A. Hyde; Edward K. Y. Jung; Chris D. Karkanias; Eric C.Leuthardt; Royce A. Levien; Richard T. Lord; Robert W. Lord; Mark A.Malamud; John D. Rinaldo, Jr.; Clarence T. Tegreene; Kristin M. Tolle;Lowell L. Wood, Jr. as inventors, filed 4 Dec. 2009, which is currentlyco-pending, or is an application of which a currently co-pendingapplication is entitled to the benefit of the filing date.

For purposes of the USPTO extra-statutory requirements, the presentapplication constitutes a continuation-in-part of U.S. patentapplication Ser. No. 12/655,250, entitled TEMPLATE MODIFICATION BASED ONDEVIATION FROM COMPLIANT EXECUTION OF THE TEMPLATE, naming Shawn P.Firminger; Jason Garms; Roderick A. Hyde; Edward K. Y. Jung; Chris D.Karkanias; Eric C. Leuthardt; Royce A. Levien; Richard T. Lord; RobertW. Lord; Mark A. Malamud; John D. Rinaldo, Jr.; Clarence T. Tegreene;Kristin M. Tolle; Lowell L. Wood, Jr. as inventors, filed 23 Dec. 2009,which is currently co-pending, or is an application of which a currentlyco-pending application is entitled to the benefit of the filing date.

For purposes of the USPTO extra-statutory requirements, the presentapplication constitutes a continuation-in-part of U.S. patentapplication Ser. No. 12/653,117, entitled SOURCE USER BASED PROVISION OFONE OR MORE TEMPLATES, naming Shawn P. Firminger; Jason Garms; RoderickA. Hyde; Edward K. Y. Jung; Chris D. Karkanias; Eric C. Leuthardt; RoyceA. Levien; Richard T. Lord; Robert W. Lord; Mark A. Malamud; John D.Rinaldo, Jr.; Clarence T. Tegreene; Kristin M. Tolle; Lowell L. Wood,Jr. as inventors, filed 7 Dec. 2009, which is currently co-pending, oris an application of which a currently co-pending application isentitled to the benefit of the filing date.

For purposes of the USPTO extra-statutory requirements, the presentapplication constitutes a continuation-in-part of U.S. patentapplication Ser. No. 12/653,180, entitled SOURCE USER BASED PROVISION OFONE OR MORE TEMPLATES, naming Shawn P. Firminger; Jason Garms; RoderickA. Hyde; Edward K. Y. Jung; Chris D. Karkanias; Eric C. Leuthardt; RoyceA. Levien; Richard T. Lord; Robert W. Lord; Mark A. Malamud; John D.Rinaldo, Jr.; Clarence T. Tegreene; Kristin M. Tolle; Lowell L. Wood,Jr. as inventors, filed 8 Dec. 2009, which is currently co-pending, oris an application of which a currently co-pending application isentitled to the benefit of the filing date.

For purposes of the USPTO extra-statutory requirements, the presentapplication constitutes a continuation-in-part of U.S. patentapplication Ser. No. 12/653,387, entitled TARGET OUTCOME BASED PROVISIONOF ONE OR MORE TEMPLATES, naming Shawn P. Firminger; Jason Garms;Roderick A. Hyde; Edward K. Y. Jung; Chris D. Karkanias; Eric C.Leuthardt; Royce A. Levien; Richard T. Lord; Robert W. Lord; Mark A.Malamud; John D. Rinaldo, Jr.; Clarence T. Tegreene; Kristin M. Tolle;Lowell L. Wood, Jr. as inventors, filed 10 Dec. 2009, which is currentlyco-pending, or is an application of which a currently co-pendingapplication is entitled to the benefit of the filing date.

For purposes of the USPTO extra-statutory requirements, the presentapplication constitutes a continuation-in-part of U.S. patentapplication Ser. No. 12/653,386, entitled TARGET OUTCOME BASED PROVISIONOF ONE OR MORE TEMPLATES, naming Shawn P. Firminger; Jason Garms;Roderick A. Hyde; Edward K. Y. Jung; Chris D. Karkanias; Eric C.Leuthardt; Royce A. Levien; Richard T. Lord; Robert W. Lord; Mark A.Malamud; John D. Rinaldo, Jr.; Clarence T. Tegreene; Kristin M. Tolle;Lowell L. Wood, Jr. as inventors, filed 11 Dec. 2009, which is currentlyco-pending, or is an application of which a currently co-pendingapplication is entitled to the benefit of the filing date.

For purposes of the USPTO extra-statutory requirements, the presentapplication constitutes a continuation-in-part of U.S. patentapplication Ser. No. 12/653,972, entitled DETECTING DEVIATION FROMCOMPLIANT EXECUTION OF A TEMPLATE, naming Shawn P. Firminger; JasonGarms; Roderick A. Hyde; Edward K. Y. Jung; Chris D. Karkanias; Eric C.Leuthardt; Royce A. Levien; Richard T. Lord; Robert W. Lord; Mark A.Malamud; John D. Rinaldo, Jr.; Clarence T. Tegreene; Kristin M. Tolle;Lowell L. Wood, Jr. as inventors, filed 17 Dec. 2009, which is currentlyco-pending, or is an application of which a currently co-pendingapplication is entitled to the benefit of the filing date.

For purposes of the USPTO extra-statutory requirements, the presentapplication constitutes a continuation-in-part of U.S. patentapplication Ser. No. 12/655,075, entitled DETECTING DEVIATION FROMCOMPLIANT EXECUTION OF A TEMPLATE, naming Shawn P. Firminger; JasonGarms; Roderick A. Hyde; Edward K. Y. Jung; Chris D. Karkanias; Eric C.Leuthardt; Royce A. Levien; Richard T. Lord; Robert W. Lord; Mark A.Malamud; John D. Rinaldo, Jr.; Clarence T. Tegreene; Kristin M. Tolle;Lowell L. Wood, Jr. as inventors, filed 21 Dec. 2009, which is currentlyco-pending, or is an application of which a currently co-pendingapplication is entitled to the benefit of the filing date.

The United States Patent Office (USPTO) has published a notice to theeffect that the USPTO's computer programs require that patent applicantsreference both a serial number and indicate whether an application is acontinuation or continuation-in-part. Stephen G. Kunin, Benefit ofPrior-Filed Application, USPTO Official Gazette Mar. 18, 2003, availableat http://www.uspto.gov/web/offices/com/sol/og/2003/week11/patbene.htm.The present Applicant Entity (hereinafter “Applicant”) has providedabove a specific reference to the application(s) from which priority isbeing claimed as recited by statute. Applicant understands that thestatute is unambiguous in its specific reference language and does notrequire either a serial number or any characterization, such as“continuation” or “continuation-in-part,” for claiming priority to U.S.patent applications. Notwithstanding the foregoing, Applicantunderstands that the USPTO's computer programs have certain data entryrequirements, and hence Applicant is designating the present applicationas a continuation-in-part of its parent applications as set forth above,but expressly points out that such designations are not to be construedin any way as any type of commentary and/or admission as to whether ornot the present application contains any new matter in addition to thematter of its parent application(s).

SUMMARY

A computationally implemented method includes, but is not limited todetermining whether a plurality of end users deviated from compliantlyexecuting a template designed to facilitate the plurality of end usersin achieving one or more target outcomes when one or more emulatableaspects included in the template are emulated by the plurality of endusers, the one or more emulatable aspects being based on one or morerelevant reported aspects of one or more source users that were deemedto have been relevant to achieving the one or more target outcomes; andmodifying the template based, at least in part, on determining that theplurality of end users deviated from compliantly executing the template.In addition to the foregoing, other method aspects are described in theclaims, drawings, and text forming a part of the present disclosure.

In one or more various aspects, related systems include but are notlimited to circuitry and/or programming for effecting theherein-referenced method aspects; the circuitry and/or programming canbe virtually any combination of hardware, software, and/or firmwareconfigured to effect the herein-referenced method aspects depending uponthe design choices of the system designer.

A computationally implemented system includes, but is not limited to:means for determining whether a plurality of end users deviated fromcompliantly executing a template designed to facilitate the plurality ofend users in achieving one or more target outcomes when one or moreemulatable aspects included in the template are emulated by theplurality of end users, the one or more emulatable aspects being basedon one or more relevant reported aspects of one or more source usersthat were deemed to have been relevant to achieving the one or moretarget outcomes; and means for modifying the template based, at least inpart, on determining that the plurality of end users deviated fromcompliantly executing the template. In addition to the foregoing, othersystem aspects are described in the claims, drawings, and text forming apart of the present disclosure.

A computationally implemented system includes, but is not limited to:circuitry for determining whether a plurality of end users deviated fromcompliantly executing a template designed to facilitate the plurality ofend users in achieving one or more target outcomes when one or moreemulatable aspects included in the template are emulated by theplurality of end users, the one or more emulatable aspects being basedon one or more relevant reported aspects of one or more source usersthat were deemed to have been relevant to achieving the one or moretarget outcomes; and circuitry for modifying the template based, atleast in part, on determining that the plurality of end users deviatedfrom compliantly executing the template. In addition to the foregoing,other system aspects are described in the claims, drawings, and textforming a part of the present disclosure.

A computer program product including a signal-bearing medium bearing oneor more instructions for determining whether a plurality of end usersdeviated from compliantly executing a template designed to facilitatethe plurality of end users in achieving one or more target outcomes whenone or more emulatable aspects included in the template are emulated bythe plurality of end users, the one or more emulatable aspects beingbased on one or more relevant reported aspects of one or more sourceusers that were deemed to have been relevant to achieving the one ormore target outcomes; and one or more instructions for modifying thetemplate based, at least in part, on determining that the plurality ofend users deviated from compliantly executing the template. In additionto the foregoing, other computer program product aspects are describedin the claims, drawings, and text forming a part of the presentdisclosure.

A method for modifying a template based, at least in part, ondetermining whether a plurality of end users deviated from compliantlyexecuting the template, the method includes determining whether aplurality of end users deviated from compliantly executing a templatedesigned to facilitate the plurality of end users in achieving one ormore target outcomes when one or more emulatable aspects included in thetemplate are emulated by the plurality of end users, the one or moreemulatable aspects being based on one or more relevant reported aspectsof one or more source users that were deemed to have been relevant toachieving the one or more target outcomes; and modifying, using aprocessor, the template based, at least in part, on determining that theplurality of end users deviated from compliantly executing the template.

The foregoing summary is illustrative only and is not intended to be inany way limiting. In addition to the illustrative aspects, embodiments,and features described above, further aspects, embodiments, and featureswill become apparent by reference to the drawings and the followingdetailed description.

BRIEF DESCRIPTION OF THE FIGURES

FIGS. 1 a and 1 b show a high-level block diagram of a Computing Device10 operating in a network environment.

FIG. 2 a shows another perspective of the Deviation Determining Module102 of the Computing Device 10 of FIG. 1 b.

FIG. 2 b shows another perspective of the Template Modifying Module 104of the Computing Device 10 of FIG. 1 b.

FIG. 3 is a high-level logic flowchart of a process.

FIG. 4 a is a high-level logic flowchart of a process depictingalternate implementations of the deviation determining operation 302 ofFIG. 3.

FIG. 4 b is a high-level logic flowchart of a process depictingalternate implementations of the deviation determining operation 302 ofFIG. 3.

FIG. 4 c is a high-level logic flowchart of a process depictingalternate implementations of the deviation determining operation 302 ofFIG. 3.

FIG. 5 a is a high-level logic flowchart of a process depictingalternate implementations of the particular template modifying operation304 of FIG. 3.

FIG. 5 b is a high-level logic flowchart of a process depictingalternate implementations of the particular template modifying operation304 of FIG. 3.

FIG. 5 c is a high-level logic flowchart of a process depictingalternate implementations of the particular template modifying operation304 of FIG. 3.

FIG. 6 is a high-level logic flowchart of another process.

FIG. 7 is a high-level logic flowchart of a process depicting alternateimplementations of the modified template presenting operation 606 ofFIG. 6.

FIG. 8 is another high-level block diagram showing one implementation ofthe computing device 10 of FIG. 1 b.

DETAILED DESCRIPTION

In the following detailed description, reference is made to theaccompanying drawings, which form a part hereof. In the drawings,similar symbols typically identify similar components, unless contextdictates otherwise. The illustrative embodiments described in thedetailed description, drawings, and claims are not meant to be limiting.Other embodiments may be utilized, and other changes may be made,without departing from the spirit or scope of the subject matterpresented here.

A recent trend that has enjoyed explosive popularity in thecomputing/communication field is to electronically record one's dailyactivities, behaviors, thoughts, beliefs, traits, physical or mentalstates, physical characteristics, and other aspects of the person'severyday life onto an open journal. One place where such open journalsare maintained is at social networking sites commonly known as “blogs”where one or more users may report or post every aspect of their dailylives. In brief, an “aspect,” as will be referred to herein, may be inreference to any act, behavior, characteristic, user state or status,belief, external events, and so forth, that may be associated with auser (e.g., a person including, for example, a network user such as ablogger or a social networking user). The process of reporting orposting blog entries is commonly referred to as “blogging.” A newer typeof blogging that has become very popular in recent times ismicroblogging, otherwise known as “twittering” or “tweeting.” Inmicroblogging, each of the microblogs that are posted are typicallyrelatively short posts or entries, usually not more than 140 characterslong.

Other types of social networking sites may also allow users to maintainopen journals and to allow users to easily update their personalinformation in real time. Such updates are typically made via, forexample, social networking status reports otherwise known simply as“status reports.” These social networking sites allow a user to reportor post for others to view the latest status or other aspects related tothe user.

Another recent tread in social networking is to employ one or moresensors to detect and report on a wide variety of user aspects (i.e.,aspects of a user). Examples of sensors that may be used for suchpurposes vary widely, ranging from well-known devices that can detectand report on various physiological parameters such as heart rate orblood pressure, to sensors that can detect certain user behaviors oractivities such as toilet usage. Examples of sensors that may beemployed in order to monitor or detect user activities include, forexample, accelerometers, pedometers, global positioning systems or GPSs,and so forth. Such devices are already, in fact, being integrated intomobile computing/communication devices such as cellular telephones andsmart phones, and even into functional devices such as automobiles,exercise machines, household appliances, and so forth.

Other types of sensors are also being integrated into mobilecomputing/communication devices such as those that monitor environmentalconditions. Examples of such sensors include, for example, those thatcan measure atmospheric conditions such as air quality levels. In somecases, sensors may be integrated into functional devices such asautomobiles, exercise machines, household appliances, and so forth inorder to detect and monitor their usage. There are also sensors that arecurrently available that can even monitor bathroom or toilet usage. Allthe above described sensors may be configured to provide their collecteddata through log entries such as entries made through social networkingchannels (e.g., microblogs, blogs, social networking internet sites, andso forth).

Although a wealth of personal information provided through log entries(e.g., microblogs, status reports, and so forth) are now availablethrough such social networking internet sites (or simply “socialnetworking sites”), it is only recently has there been any effort toexploit such potentially useful data. As blogs, microblogs, and varioussocial networking sites become increasingly popular, personal datacollected through such means may be spread across multiple networklocations.

One possible way to exploit such personal data is to use such data todevelop templates for achieving a variety of target outcomes (e.g.,goals) based on the personal data. In brief, a template may be a plan, aprogram, or a schedule that is designed to facilitate one or more endusers to achieve one or more target outcomes when one or more“emulatable aspects” that may be included with the template areemulated. In other words, to use personal data of those (e.g., sourceusers) who have already achieved desirable goals (e.g., target outcomes)to develop templates for others (e.g., end users) to emulate in order tofacilitate the others in achieving those goals.

Each of the one or more emulatable aspects that may be included in atemplate may be based on and correspond to one or more reported aspectsof one or more source users that may have been reported through, forexample, social networking channels (e.g., microblogs, social networkingsites, and so forth). An “aspect,” in brief may be any behavior, act,mental state, physical state, and so forth that may be associated with asource user. A “reported aspect” is any aspect associated with a sourceuser that may have been reported via, for example, one or more socialnetworking channels or by other means.

There are at least two types of templates that could be developed frompersonal data obtained through, for example, social networking channels.One type of templates are generic templates that may not be designed foruse by any particular end user or a particular group of end users butinstead may be designed to be used by any random user in order toachieve one or more target outcomes. The second type of templates, whichmay be referred to as personalized templates or personalized plans,include those templates that have been personalized for use by aparticular end user or users (e.g., a modified version of a generictemplate that has been modified in order to accommodate the end user'slimitations and/or preferences). For purposes of this description,references to a “template” in the following will be in reference toeither the first or the second type of templates.

In any event, once a template for achieving one or more target outcomeshas been developed, the developed template, which could be a generictemplate or a personalized template, may be provided to one or more endusers. An end user may then compliantly execute (i.e., properly execute)the provided template by fully or partially emulating all or some of theone or more emulatable aspects that may be included in the template inorder to achieve the one or more target outcomes. Of course, if an enduser is unable to compliantly emulate the template, than the one or moretarget outcomes associated with the template may or may not be realized.In many cases, however, it may still be possible to achieve the targetoutcomes associated with templates even if end users do not compliantlyexecute the templates.

What constitutes compliant execution of a template will depend on anumber of factors including, for example, the type of template beingemulated and the number and type of emulatable aspects that may beincluded in the template. For example, in some cases, the compliantexecution of a template may require full and complete emulation of eachof the one or more emulatable aspects that may be included in thetemplate (e.g., if the template requires 45 minutes of running everyother day for two months, than to compliantly emulate the template anend user must execute 45 minutes of running every other day for twomonths).

In other cases, however, the compliant execution of a template maymerely require that each of the one or more emulatable aspects that maybe included in the template be at least substantially emulated or atleast only partially emulated (e.g., in the same example above, acompliant execution of the template may be achieved if, for example, onsome occasions the end user runs 30 minutes rather than 45 minutes). Instill other cases, the compliant execution of a template may onlyrequire that a substantial portion of a plurality of emulatable aspectsthat may be included in the template be fully or substantially emulated(e.g., in the above example, a compliant execution of the template maybe achieved even if one or more two days of running are not emulated bythe end user).

For purposes of this description, and unless indicated otherwise, thephrase “compliant execution of a template” may be in reference to acomplete or substantially complete emulation of each of the one or moreemulatable aspects that may be included the template. Further, in somecases, the “compliant execution of a template” may be in reference to aplurality of emulatable aspects that may be included in the template tobe completely or substantially completely emulated in the order (e.g.,sequential order) that is specified by the template.

In some cases, it may be possible to achieve one or more target outcomesof a template without strictly or compliantly executing the template.That is, upon end users executing a particular template, some end usersmay deviate from complete and total emulation of each of the one or moreemulatable aspects that may be included in the particular template whilestill achieving the target outcomes.

In various embodiments, methods, systems, circuitry, and computerprogram products are provided that are designed to modify a templatebased on feedback provided by end users. More particularly, the methods,systems, circuitry, and computer program products may be designed to,among other things, modify a template based, at least in part, ondetermining that a plurality of end users deviated from compliantlyexecuting the template. In some embodiments, the determining of thedeviation may involve, for example, at least acquiring and processinglog entry data (e.g., as acquired through blogs, microblogs, socialnetworking internet sites, and so forth) associated with those end userswho have deviated from the compliant execution of the template whilestill achieving the one or more target outcomes associated with thetemplate. In some embodiments, the modification of the template may bebased, at least, on the processing of the log entry data.

As previously described a “template” may be any type of plan, program,or schedule that is designed to facilitate achievement of one or moretarget outcomes when one or more emulatable aspects included in thetemplate are emulated. Of course, and as briefly described above, insome cases, it may also be possible to achieve one or more targetoutcomes of a template without fully emulating all of the one or moreemulatable aspects that may be included in the template or even failingto emulate a portion of a plurality of emulatable aspects that may beincluded in the template. As also indicated earlier, the one or moreemulatable aspects that may be included in a template may be based onand correspond to one or more reported aspects of one or more sourceusers, who may or may not be the source for the one or more reportedaspects. That is, a reported aspect may be reported by any one of anumber of different sources including, for example, by the source user(e.g., a microblogger or a social networking user) who is the basis forthe reported aspect, by a sensor, or by a third party (e.g., such asanother source user). Similarly, reported aspects of an end user, suchas reported aspects of the end user while the end user is executing atemplate, may also be provided by a number of different sources. Suchreported aspects of the end user may be used, in some cases, as end userfeedback in order to modify or further develop a template.

As described, a template may comprise of one or more emulatable aspectsthat may be based on reported aspects of, for example, a particularsource user. Note that the word “emulatable” as will be repeatedly usedherein has no relevant meaning other than to be used in the followingdescription to merely distinguish those aspects (emulatable aspects)that are indicated in a template from other types of aspects (e.g.,reported aspects of source users or end users). In accordance withvarious embodiments, a template may be developed for achieving almostany type of desired outcome (e.g., target outcome) so long as theappropriate data, such as log entry data of source users who haveachieved the desired outcome, are available. Examples of the types oftemplates that could be developed based on log entry data include, forexample, those that are designed to facilitate achievement of medical orhealth related outcomes, those that are designed to facilitateachievement of athletic or gaming outcomes, those that designed tofacilitate achievement of particular user states such as mental orsocial states, those that are designed to facilitate achievement ofintellectual or academic outcomes, and so forth.

In some cases, a template may merely indicate or be a collection of oneor more emulatable aspects that end users may emulate in order toachieve one or more target outcomes. In other cases, however, a templatemay indicate a plurality of emulatable aspects as well as define theirrelationships (e.g., temporal or specific time relationship) withrespect to each other. Such a template will be very similar to aschedule or program that indicates when each of the emulatable aspectsincluded in the template should be emulated by end users with respect tothe other emulatable aspects included in the template. For example, if atemplate is designed to facilitate end users to shed a certain amount ofbody weight, it may include a schedule of when and what activities(e.g., go jogging for 30 minutes on day 1, go swimming for 40 minutes onday 2, and so forth) end users may need to execute in order to achievethe weight loss. Similarly, if the template is designed to, for example,facilitate end users to achieve a high score for the scholastic aptitudetest (SAT), the template may be a schedule of when and what activities(e.g., read a particular book on day 1, work on math problems from aparticular math book on day 2, and so forth) end users may need toexecute in order to achieve the high test score for the SAT.

In some instances a template may include one or more emulatableintermediate outcomes that are related to the one or more targetoutcomes associated with the template. For example, in the above weightloss example, the template may indicate the amount of weight loss endusers should have achieved (e.g., in order to achieve the targetoutcome) after emulating, for example, one week, two weeks, or a monthof emulatable aspects indicated by the template.

In still other cases, a template may merely be a collection ofemulatable aspects that does not define the relationships between theemulatable aspects. For example, a template designed to facilitate anend user to achieve relaxed state of mind may indicate two unlinkedemulatable aspects, “get 8 hours of sleep each night,” and “avoidcaffeine beverages.” Such a template would not necessarily have anyindication of relationship between the two emulatable aspects indicatedby the template. It should be noted here that an emulatable aspect thatmay be included into a template may not only be an act or a behavior,but may be a physiological characteristic, a mental state, or any otheraspect that may be emulated. For example, a template that is designed tofacilitate reducing backaches may include as one of its aspects, arequirement to keep blood pressure below a certain level, which is aphysiological state. An emulatable aspect may even be an external event,such as environmental conditions, that an end user may have some controlover.

In some embodiments, a template may include or be linked to otherinformation other than emulatable aspects. For example, in someinstances, a template may include or be associated with a particularsource user and/or with a particular target outcome. Other informationmay also be included with or be associated with a template as will befurther described herein.

In order to facilitate understanding of the various concepts to bedescribed herein, an introduction to the meaning of certain words andphrases to be used in the following discussion will now be provided. Inbrief, and as will be further described herein, an “aspect” may be anyoccurrence of any behavior, act, belief, characteristic, state, externalevent, or any other facet associated with a source user or a group ofsource users. A “source user” may be any person, such as a microbloggeror a social networking user, who may be the basis for one or morereported aspects. Note that a source user may not necessarily have to bethe source for the one or more reported aspects that are related to thesource user since reported aspects that are associated with a particularsource user may be provided by other source users or by sensors.

A “reported aspect” may be any aspect associated with or related to asource user or an end user that has been reported by, for example, thesource user, the end user, by one or more sensors, or one or more thirdparties (e.g., other source users or end users). In some instances, sucha reported aspect may be reported in the form of a log entry such as amicroblog entry, a status report, or a journal entry.

A “target outcome” may be any type of desirable goal or result that maybe sought by, for example, end users. Examples of target outcomesinclude, for example, health-related outcomes such as weight loss orimproved cardiovascular conditioning, athletic outcomes such asdeveloping a particular athletic skill including being able to pitch acurve ball or achieving a particular golf handicap, physiologicaloutcomes such as reduced blood pressure or blood glucose levels, socialoutcomes such as obtaining membership into an elite social club orattaining a particular social status, mental state outcomes such asachieving certain level of calmness or happiness, interpersonal orrelational outcomes such as having lots of friends or developing skillto make friends, employment outcomes such as being promoted ordeveloping certain work skills, academic or intellectual outcomes, andso forth.

An “end user” may be any person, for example, who executes a template inorder to achieve one or more target outcomes. As briefly describedabove, a “source user” may be any person who may be the basis for one ormore reported aspects. Note that although in most cases, a source userwill be an actual (real) person who may be the basis for one or morereported aspects, in other cases, however, a source user may be afictional person such as a composite of multiple “actual” source users.For example, reported aspects indicating actual aspects of a pluralityof actual source users may be compiled and processed (e.g., normalizedor averaged out) in order to create a fictional source user.

Turning now to FIGS. 1 a, and 1 b illustrating an example environment inwhich the methods, systems, circuitry, and computer program products inaccordance with various embodiments may be implemented by a computingdevice 10. In particular, the methods, systems, circuitry, and computerprogram products may be implemented at any network device including at apeer-to-peer network component device. In some embodiments, thecomputing device 10 may be a server such as one of the one or morenetwork servers 60 illustrated in FIG. 1 a. Alternatively, the computingdevice 10 may be a source user device such as one of the local sourceuser devices 20* illustrated in FIG. 1 a. In still other embodiments,the computing device 10 may be an end user device such as one of thelocal end user device 30* illustrated in FIG. 1 a. Note that in thefollowing, “*” represents a wildcard. Thus, references in the followingdescription to, for example, “a source user 2*” may be in reference to asource user 2 a, a source user 2 b, and so forth, or a combinationthereof.

Note further that for ease of understanding and explanation, thecomputing device 10 of the exemplary environment 100 of FIGS. 1 a and 1b in the following discussion will be generally described operating as aserver (e.g., server embodiment) rather than as an end user device or asa source user device. Further, although the following discussion relatedto the exemplary environment 100 of FIG. 1 a and 1 b assumes that thecomputing device 10 is a server, the following discussion will, for themost part, be applicable even if the computing device 10 were operatingas an end user device (e.g., local end user device 30*) or as a sourceuser device (e.g., local source user device 20*) with certain obviousexceptions (e.g., if the computing device 10 is an end user device or asource user device rather than a server, the computing device 10 maycommunicate with an end user 4* or a source user 2* directly through auser interface 120 rather than indirectly through one or morecommunication networks 50 as may be the case when the computing device10 is a server). In some embodiments, the computing device 10 mayoperate via a web 1.0 or web 2.0 construct.

Referring back to FIGS. 1 a and 1 b, and as previously indicated, thecomputing device 10 may be a network device such as a server (e.g., anetwork server 60) that is designed to communicate with other networkdevices. For example, the computing device 10 may communicate with oneor more source users 2* (e.g., source user 2 a, source user 2 b, and soforth) through one or more local source user devices 20* (e.g., localsource user device 20 a, local source user device 20 b, and so forth),with a plurality of end users 4* (e.g., end user 4 a, end user 4 b, andso forth) through a plurality of local end user devices 30* (e.g., localend user device 30 a, local end user device 30 b, and so forth), withone or more sensor integrated devices 40 (e.g., a transportation vehiclesuch as a car, an exercise machine, or any other type of functionaldevice that may have an integrated sensor designed to sense, forexample, usage), with one or more network servers 60, and/or with one ormore third parties 6 (e.g., one or more content providers, one or morenetwork service providers, and/or one or more other end users 4) via oneor more communication networks 50. In some implementations, the one ormore communication networks 50 may include one or more wireless networksand/or one or more wired networks including, for example, at least oneof a local area network (LAN), a wireless local area network (WLAN),personal area network (PAN), Worldwide Interoperability for MicrowaveAccess (WiMAX), public switched telephone network (PTSN), general packetradio service (GPRS), cellular networks, and/or other types of wirelessand/or wired networks.

In some implementations, the computing device 10 may be designed todevelop at least one template 16 that is designed to facilitateachievement of one or more target outcomes when one or more emulatableaspects included in the template 16 are emulated. The development of thetemplate 16 may be based on one or more source user log entries 12 thatmay indicate one or more reported aspects associated with one or moresource users 2* and that may be received from a variety of sourcesincluding for example, one or more network servers 60, one or more localsource user devices 20*, one or more sensor integrated devices 40,and/or one or more third parties 6. In some cases, such source user logentries 12 may be in the form of, for example, social networking entriessuch as blog entries (e.g., microblog entries), status reports, and soforth. After receiving the one or more source user log entries 12indicating the one or more reported aspects associated with the one ormore source user 2*, the template 16 may be developed by at leastidentifying from the one or more reported aspects one or more relevantreported aspects that are deemed to be relevant to achieving the one ormore target outcomes. Once the relevant reported aspects have beenidentified, the template 16 may be developed (e.g., created) by at leastincluding into the template 16 one or more emulatable aspects thatcorrespond to the one or more relevant reported aspects. In some cases,the development of the template 16 may further include defining in thetemplate 16 the relationships (e.g., temporal or specific timerelationships) between a plurality of emulatable aspects that may beincluded in the template 16.

After developing the template 16, the template 16 may be provided to atleast one end user 4, to one or more network servers 60, to one or morethird parties 6, or to one or more source users 2* via one or morecommunication networks 50. In embodiments in which the computing device10 is a local client device such as local end user device 30* or a localsource user device 20*, the template 16 may be presented via a userinterface 120.

In alternative implementations, however, the template 16 may not bedeveloped at the computing device 10, but instead, may be provided tothe computing device 10 from a remote network site (e.g., a local sourceuser device 20*, a network server 60, a local end user device 30*, andso forth) through, for example, one or more communication networks 50.

In various implementations, after developing or being provided with atemplate 16, the computing device 10 may be designed to monitor theprogress of, for example, a plurality of end users 4* in compliantlyexecuting the template 16 in order to achieve the one or more targetoutcomes associated with the template 16. In particular, such monitoringmay be performed in order to determine any deviation by the end users 4*from a compliant execution of the template 16.

In order to monitor the progress of the end users 4* in compliantlyexecuting the template 16, the computing device 10 may be designed toreceive one or more end user log entries 14 (e.g., in the form of, forexample, microblogs, status reports, journal entries, sensor entries,and so forth) associated with the end users 4* from one or more sources(e.g., local end user devices 30*, one or more sensor integrated devices40, one or more third parties 6 such as other end users 4* and/or one ormore network servers 60). The end user log entries 14 to be received mayindicate a plurality of reported aspects of a plurality of end users 4*when the end users 4* are, for example, executing the template 16. Notethat in embodiments in which the computing device 10 is an end userdevice (e.g., local end user device 30), one or more of the end user logentries 14 may be received directly from an end user 4* via the userinterface 120.

In order to determine deviation from the compliant execution of thetemplate 16 by the plurality of end users 4*, the reported aspectsindicated by the received end user log entries 14 may be compared to theone or more emulatable aspects of the template 16. By making thecomparison, a determination may be made as to whether one or moredeviations from the one or more emulatable aspects included in thetemplate 16 may have occurred. By at least determining that one or moredeviations from the one or more emulatable aspects of the template 16have occurred, a determination may be made that one or more deviationsfrom the compliant emulation of the template 16 may have also occurred.

In any event, after determining or detecting deviation from thecompliant execution of the template 16 by a plurality of end users 4*,the computing device 10 may be designed to modify the template 16resulting in a modified template 18. The template 16 may be modified ina number of different ways in various alternative implementations. Forexample, in some implementations, the template 16 may be modified bymodifying at least one of one or more emulatable aspects included in thetemplate 16. In some instances, the modification of at least one of theone or more emulatable aspects may involve revising at least one of theone or more emulatable aspects, replacing at least one of the one ormore emulatable aspects with one or more replacement or substituteemulatable aspects, or deleting at least one of the one or moreemulatable aspects. In some implementations, a template 16 may bemodified by adding one or more additional emulatable aspects. Inimplementations where a template 16 includes multiple emulatableaspects, the template 16 may be modified by modifying the one or morerelationships (e.g., temporal or specific time relationships) betweenthe plurality of emulatable aspects included in the template 16. Otherways of modifying a template 16 may also be employed in variousalternative implementations.

In some implementations, the template 16 may be modified (e.g., bysubstituting or modifying existing emulatable aspects, or by addingadditional emulatable aspects) in order to include at least oneplausible emulatable aspect that was successfully emulated by at least aportion of a plurality of end users 4* who were determined to havedeviated from the compliant execution of the template 16. In the same ordifferent implementations, the template 16 may be modified in order toinclude at least one emulatable aspect that was developed by processingreports aspects (e.g., as indicated by end user log entries 14) of endusers 4* who were determined to have deviated from the compliantexecution of the template 16. These various approaches for modifying atemplate 16 as well as other approaches for modifying the template 16will be discussed in greater detail herein. In some implementations, thetemplate 16 may be modified to include one or more emulatable aspectsbelonging to a wide variety of emulatable aspect types (e.g., emulatablebehaviors such as emulatable user activities, user attitudes, and userconduct, emulatable user beliefs, emulatable user states, and so forth).

As a result of modifying the template 16, a modified template 18 may begenerated by the computing device 10. In some cases, the modifiedtemplate 18 may be presented to, for example, at least one of the endusers 4*, one or more network servers 60, and/or one or more thirdparties 6 via the one or more communication networks 50 and/or via theuser interface 120.

In various embodiments, the computing device 10, as previouslyindicated, may be a server (e.g., one of the one or more network servers60) that may be located at a single network site, located acrossmultiple network sites, or may be a conglomeration of servers located atmultiple network sites. In embodiments in which the computing device 10is a source user device (e.g., local source user device 20*) or an enduser device (e.g., local end user device 30*) rather than a networkserver 60, the computing device 10 may be any one of a wide range ofmobile or stationary computing/communication devices including, forexample, a laptop, a desktop, a workstation, a cellular telephone, apersonal digital assistant (PDA), a Smartphone, a web tablet such as aNetbook, and so forth.

Referring back to the exemplary environment 100 of FIGS. 1 a and 1 b,the one or more sensor integrated devices 40 of the exemplaryenvironment 100 of FIGS. 1 a and 1 b may directly communicate with theone or more communication networks 50 in various embodiments.Alternatively, the one or more sensor integrated devices 40 mayindirectly communicate with the one or more communication networks 50via the one or more local source user devices 20* or via the one or morelocal end user devices 30* (e.g., via, for example, personal areanetwork or PAN). In various embodiments, a sensor integrated device 40may be a variety of functional devices that may comprise of one or moresensors 140 and that may be operated or used by a source user 2* or byan end user 4*. Examples of such devices include, for example, atransportation vehicle (e.g., automobile, a motorcycle, a boat, a plane,and so forth), an exercise machine (e.g., a treadmill), a householdappliance (e.g., television set), and so forth.

As will be further described herein, the one or more sensors 140, whichmay also be included in the one or more local source user devices 20*,the local end user devices 30*, and/or the computing device 10, mayinclude any type of sensors 140 that can sense one or more aspects of asource user 2* or an end user 4*. Examples of such sensors 140 include,for example, sensors 140 that can sense various physical characteristicsof a source user 2* or an end user 4* (e.g., heart rate sensor or bloodpressure sensor), sensors 140 that can sense activities of a source user2* or an end user 4* (e.g., a pedometer, an accelerometer, and soforth), sensors 140 that can sense environment conditions (e.g., airquality sensors), sensors 140 that can sense the location of a sourceuser 2* or an end user 4* (e.g., global positioning system or GPS),sensors 140 that can provide physiological data that may be processed inorder to determine inferred mental states of source or end users 2* or4*, and so forth.

Each of the one or more local source user devices 20* and the local enduser devices 30* (as well as the computing device 10 in embodiments inwhich the computing device 10 is an end user device or a source userdevice) may be any one of a variety of computing/communication devicesincluding, for example, a cellular phone, a personal digital assistant(PDA), a laptop, a desktop, or other types of computing/communicationdevices. In some embodiments, the one or more local source user devices20* and/or the local end user devices 30* (as well as the computingdevice 10 in some embodiments) may be a handheld device such as acellular telephone, a Smartphone, a Mobile Internet Device (MID), anUltra Mobile Personal Computer (UMPC), a convergent device such as apersonal digital assistant (PDA), and so forth. Alternatively, suchlocal client devices (e.g., local source user device 20* and/or localend user devices 30*) may be a laptop, a desktop, a workstation, a webtablet such as a Netbook, or other types of devices that may not be ahandheld device in various alternative implementations.

The computing device 10 as illustrated in FIG. 1 b may include one ormore modules, sub-modules, and various other components. As shown, thecomputing device 10 may include at least a deviation determining module102 (which may further include one or more sub-modules as illustrated inFIG. 2 a) and a template modifying module 104 (which may also includeone or more sub-modules as illustrated in FIG. 2 b). The deviationdetermining module 102 may be particular configured to, among otherthings, determine whether a plurality of end users 4* deviated fromcompliantly executing a template 16 designed to facilitate the pluralityof end users 4* in achieving one or more target outcomes when one ormore emulatable aspects included in the template 16 are emulated by theplurality of end users 4*, the one or more emulatable aspects beingbased on one or more relevant reported aspects of one or more sourceusers 2* that were deemed to have been relevant to achieving the one ormore target outcomes. In contrast, the template modifying module 104 maybe particularly configured to, among other things, modify the template16 based, at least in part, on determining that the plurality of endusers 4* deviated from compliantly executing the template 16.

In various implementations, the computing device 10 may further includea template developing module 103 and a memory 116. The templatedeveloping module 103 may be particularly configured to develop one ormore templates 16 by at least initially identifying or determining oneor more relevant reported aspects of one or more source user 2* thathave been determined to be relevant for achieving one or more targetoutcomes. After identifying one or more relevant reported aspects, thetemplate developing module 103 may be particularly configured to develop(e.g., create) a template 16 by at least including into the template 16one or more emulatable aspects that correspond to the one or moreidentified relevant reported aspects. The determination of relevancy ofa reported aspect associated with one of the source users 2* may bebased on a number of factors including, for example, whether it is atype of reported aspect that is of interest to end users 4* or sourceusers 2* and whether the reported aspect occurred proximate to theoccurrence of the one or more target outcomes as achieved by the sourceuser 2*.

The memory 116, in various implementations, may store a plurality oftemplates 14 including a template 16 and/or a modified template 18 thatis a modified version of template 16. In some implementations, thememory 116 may store one or more applications 140 (e.g., a textmessaging application, an instant messaging application, an emailapplication, a social networking application, a voice recognitionsystem, a Web 1.0 application, and/or Web 2.0 application to facilitatein communicating via, for example, the World Wide Web). The memory 116may comprise of one or more of a mass storage device, a read-only memory(ROM), a programmable read-only memory (PROM), an erasable programmableread-only memory (EPROM), a cache memory such as random access memory(RAM), a flash memory, a synchronous random access memory (SRAM), adynamic random access memory (DRAM), and/or other types of memorydevices.

The computing device 10 may also include, in various implementations, anetwork interface 118 (e.g., a network interface card or NIC), a userinterface 120 (e.g., a display monitor, a touchscreen, a microphone, aspeaker, a mouse, and so forth), and/or one or more sensors 140 that aredesigned to measure or sense one or more user aspects. Examples ofsensors 140 include, for example, devices that are designed to senseuser activities such as pedometers and accelerometers, devices that aredesigned to sense physiological characteristics such as heart ratemonitors or blood glucose monitors, devices that are designed to senseenvironmental conditions such as sensors 140 for measuring air quality,devices that are designed to detect user location such as GPS, and soforth. In some cases, the presence or absence of some of these modulesand components of computing device 10 may depend on, for example,whether the computing device 10 is a server, an end user device, or asource user device. For example, if the computing device 10 is a server,then the computing device 10 may not include a user interface 120.

FIG. 2 a illustrates particular implementations of the deviationdetermining module 102 of FIG. 1 b. The deviation determining module 102in various implementations may include, among other things, a reportedaspect data receiving module 202 particularly configured for, amongother things, receiving data indicating reported aspects of end users4*, a comparing module 218 particularly configured to compare reportedaspects of end users 4* with one or more emulatable aspects included ina template 16, and/or an emulatable aspect identifying module 220particularly configured to, among other things, identify which of theone or more emulatable aspects included in template 16 were not emulatedat all or only partially emulated by one or more of the end users 4*based on the comparison of the reported aspects with the one or moreemulatable aspects included in the template 16.

The deviation determining module 102 may also include, in variousimplementations, an end user identifying module 222 particularlyconfigured to, among other things, identify which of the plurality ofend users 4* did not emulate at all or only partially emulated the oneor more emulatable aspects included in the template 16 that wereidentified by the emulatable aspect identifying module 220 as being notemulated at all or were only partially emulated by one or more of theend users 4*, a reported aspect identifying module 224 particularlyconfigured to, among other things, identify which of the reportedaspects of the plurality of end users 4* represent one or morereplacement aspects for one or more emulatable aspects included in thetemplate 16, and/or a particular order determining module 226 that isspecifically designed to, among other things, determine whether theplurality of end users 4* did not emulate a plurality of emulatableaspects included in the template 16 in a particular order as defined bythe template 16.

In various implementations, the reported aspect data receiving module202 may further include one or more sub-modules including for example, anetwork receiving module 204 (designed to, among other things, receivedata indicating at least one reported aspect associated with at leastone end user 4* from one or more communication networks 50), a userinterface receiving module 206 (designed to, among other things, receiveat least one reported aspect associated with at least one end user 4*via a user interface 120), and/or a log entry receiving module 208(designed to, among other things, receive data indicating at least onereported aspect associated with at least one end user 4* via one or moreend user log entries 14).

The log entry receiving module 208, in various implementations, mayfurther include a social networking entry receiving module 210 (whichmay further include a blog entry receiving module 212 and/or a statusreport receiving module 214) and/or a journal entry receiving module216. The social networking entry receiving module 210 may be configuredto receive the data indicating the at least one reported aspectassociated with the at least one end user 4* via one or more socialnetworking entries. The blog entry receiving module 212 may beconfigured to receive the data indicating the at least one reportedaspect associated with the at least one end user 4* via one or more blogentries. The status report receiving module 214 may be configured toreceive the data indicating the at least one reported aspect associatedwith the at least one end user 4* via one or more social networkingstatus reports. The journal entry receiving module 216, in contrast, maybe configured to receive the data indicating the at least one reportedaspect associated with the at least one end user 4* via one or morejournal entries.

FIG. 2 b illustrates particular implementations of the templatemodifying module 104 of the computing device 10 of FIG. 1 b. Asillustrated, the template modifying module 104 may include, in variousimplementations, an emulatable aspect modifying module 230 (which mayfurther include an emulatable aspect revising module 232, an emulatableaspect replacing module 234, and/or an emulatable aspect deleting module236). As further illustrated, in some implementations the templatemodifying module 104 may also include an emulatable aspect adding module238 (which may further include a relationship defining module 240), arelationship modifying module 242, and/or a reported aspect analyzingmodule 243. In some implementations the reported aspect analyzing module243 may further include a mean value emulatable aspect developing module246 and/or an average value emulatable aspect developing module 248.These modules and sub-module of the template modifying module 104, aswell as the modules and sub-modules of the deviation determining module102 of FIG. 2 a, will be discussed in greater detail below with respectto the processes and operation to be described herein.

Referring back to the computing device 10 of FIG. 1 b, the variousmodules (e.g., the deviation determining module 102, the templatemodifying module 104, and so forth) along with their sub-modulesincluded in the computing device 10 may be implemented using hardware,software, firmware, or any combination thereof. For example, in someimplementations, the deviation determining module 102 and/or thetemplate modifying module 104 may be implemented with a processor 802(e.g., microprocessor, controller, and so forth) executing computerreadable instructions 804 (e.g., computer program product) stored in astorage medium 806 (e.g., volatile or non-volatile memory) such as asignal-bearing medium as depicted in the computing device 10 of FIG. 8.Alternatively, hardware such as application specific integrated circuit(ASIC) may be employed in order to implement such modules in somealternative implementations.

A more detailed description of the computing device 10 of FIG. 1 b andits components will now be provided with respect to the processes andoperations to be described herein. FIG. 3 illustrates an operationalflow 300 representing example operations directed to, among otherthings, modification of a template 16 based, at least in part, ondetermining whether a plurality of end users 4* deviated fromcompliantly executing the template 16 that is designed to facilitate theplurality of end users 4* to achieve one or more target outcomes whenone or more emulatable aspects included in the template 16 or emulated.In various implementations, the plurality of end users 4* may have stillachieved the one or more target outcomes associated with the template 16even though the end users 4* may have deviated from the compliantexecution of the template 16.

In FIG. 3 and in the following figures that include various examples ofoperational flows, discussions and explanations of the operational flowswill be provided with respect to the exemplary environment 100 describedabove as illustrated in FIGS. 1 a and 1 b, and/or with respect to otherexamples (e.g., as provided in FIGS. 2 a and 2 b) and contexts. However,it should be understood that the operational flows may be executed in anumber of other environments and contexts, and/or in modified versionsof FIGS. 1 a, 1 b, 2 a, and 2 b. Also, although the various operationalflows are presented in the sequence(s) illustrated, it should beunderstood that the various operations may be performed in other ordersother than those which are illustrated, or may be performedconcurrently.

Further, in FIG. 3 and in the figures to follow thereafter, variousoperations may be depicted in a box-within-a-box manner. Such depictionsmay indicate that an operation in an internal box may comprise anoptional example embodiment of the operational step illustrated in oneor more external boxes. However, it should be understood that internalbox operations may be viewed as independent operations separate from anyassociated external boxes and may be performed in any sequence withrespect to all other illustrated operations, or may be performedconcurrently.

In any event, after a start operation, the operational flow 300 may moveto a deviation determining operation 302 for determining whether aplurality of end users deviated from compliantly executing a templatedesigned to facilitate the plurality of end users in achieving one ormore target outcomes when one or more emulatable aspects included in thetemplate are emulated by the plurality of end users, the one or moreemulatable aspects being based on one or more relevant reported aspectsof one or more source users that were deemed to have been relevant toachieving the one or more target outcomes. For instance, and as anillustration, the deviation determining module 102 of the computingdevice 10 of FIG. 1 b determining whether a plurality of end users 4*deviated from compliantly executing a template 16 designed to facilitatethe plurality of end users 4* in achieving one or more target outcomes(e.g., health or medical outcomes, user state outcomes, employment orleisure outcomes, and so forth) when one or more emulatable aspectsincluded in the template 16 are emulated by the plurality of end users4*, the one or more emulatable aspects being based on one or morerelevant reported aspects (e.g., as indicated by source user log entries12) of one or more source users 2* that were deemed to have beenrelevant to achieving the one or more target outcomes.

In addition to the deviation determining operation 302, operational flow300 may also include a template modifying operation 304 for modifyingthe template based, at least in part, on determining that the pluralityof end users deviated from compliantly executing the template. Forinstance, the template modifying module 104 of the computing device 10modifying the template 16 based, at least in part, on determining thatthe plurality of end users 4* deviated from compliantly executing thetemplate 16. In various implementations, end user data such as dataobtained through end user log entries 14 that indicate reported aspectsof the plurality of end users 4* may be processed in order to facilitatein the modification of the template 16. Such processing may beimplemented in order to, for example, determine the type of emulatableaspects that may be included in the modified template 18. In variousimplementations, the deviation determining operation 302 and thetemplate modifying operation 304 of FIG. 3 may be executed in a numberof different ways.

For example, FIGS. 4 a, 4 b, and 4 c illustrate various ways that thedeviation determining operation 302 of FIG. 3 may be executed in variousalternative implementations. For instance, the deviation from thecompliant execution of the template 16 by the plurality of end users 4*to be determined through the deviation determining operation 302 may beaccomplished in a variety of different ways. In some implementations,for example, the deviation determining operation 302 of FIG. 3 mayinclude an operation 402 for determining whether the plurality of endusers deviated from compliantly executing the template by at leastreceiving data indicating reported aspects of the plurality of end usersas depicted in FIG. 4 a. For instance, the deviation determining module102 including the reported aspect data receiving module 202 (see FIG. 2a) of the computing device 10 determining whether the plurality of endusers 4* deviated from compliantly executing the template 16 when thereported aspect data receiving module 202 at least receives dataindicating reported aspects (e.g., dietary activities, exerciseactivities, mental states, medical treatment, and so forth) of theplurality of end users 4*. In some implementations, the reported aspectsof the plurality of end users 4* may be the reported aspects of the endusers 4* when the end users 4* were executing the template 16.

Operation 402 for receiving the data that indicates the reported aspectsof the plurality of end users 4* may be executed in a number of ways.For example, in some implementations, operation 402 may include anoperation 403 for receiving the data indicating the reported aspects ofthe plurality of end users including receiving data indicating at leastone of the reported aspects from one or more communication networks asdepicted in FIG. 4 a. For instance, the reported aspect data receivingmodule 202 including the network receiving module 204 of the computingdevice 10 receiving the data indicating the reported aspects of theplurality of end users 4* including receiving by the network receivingmodule 204 of data (e.g., end user log entries 14) that indicates atleast one of the reported aspects from one or more communicationnetworks 50.

In the same or different implementations, operation 402 may include anoperation 404 for receiving the data indicating the reported aspects ofthe plurality of end users including receiving data indicating at leastone of the reported aspects via a user interface as depicted in FIG. 4a. For instance, the reported aspect data receiving module 202 includingthe user interface receiving module 206 of the computing device 10 whenthe computing device 10 is an end user device (e.g., local end userdevice 30*) receiving the data indicating the reported aspects of theplurality of end users 4* including receiving by the user interfacereceiving module 206 of data indicating at least one of the reportedaspects via a user interface 120 (e.g., a keyboard or keypad, amicrophone, a mouse, a touchscreen, and so forth).

In the same or different implementations, operation 402 may include anoperation 405 for receiving the data indicating the reported aspects ofthe plurality of end users including receiving data indicating at leastone of the reported aspects via one or more end user log entries asdepicted in FIG. 4 a. For instance, the reported aspect data receivingmodule 202 including the log entry receiving module 208 of the computingdevice 10 receiving the data indicating the reported aspects of theplurality of end users 4* including receiving by the log entry receivingmodule 208 of data indicating at least one of the reported aspects viaone or more end user log entries 14.

Operation 405, in turn, may further include one or more additionaloperations in various alternative implementations. For example, in someimplementations, operation 405 may include an operation 406 forreceiving the data indicating at least one of the reported aspects viaone or more social networking entries as depicted in FIG. 4 a. Forinstance, the social networking entry receiving module 210 of thecomputing device 10 receiving the data indicating at least one of thereported aspects via one or more social networking entries.

In some implementations, operation 406 may further include an operation407 for receiving the data indicating at least one of the reportedaspects via one or more blog entries as depicted in FIG. 4 a. Forinstance, the blog entry receiving module 212 of the computing device 10receiving the data indicating at least one of the reported aspects viaone or more blog entries (e.g., microblog entries).

In the same or different implementations, operation 406 may include anoperation 408 for receiving the data indicating at least one of thereported aspects via one or more status reports as depicted in FIG. 4 a.For instance, the status report receiving module 114 of the computingdevice 10 receiving the data indicating at least one of the reportedaspects via one or more (social networking) status reports.

In some implementations, operation 405 for receiving the data indicatingat least one of the reported aspects via one or more end user logentries may include an operation 409 for receiving the data indicatingat least one of the reported aspects via one or more journal entries asdepicted in FIG. 4 a. For instance, the journal entry receiving module216 of the computing device 10 receiving the one or more end user logentries 14 including the journal entry receiving module 216 receivingthe data indicating at least one of the reported aspects via one or morejournal entries.

In the same or different implementations, operation 405 may include anoperation 410 for receiving the one or more end user log entriesincluding the data indicating at least one of the reported aspects fromone or more of the end users as depicted in FIG. 4 a. For instance, thelog entry receiving module 208 of the computing device 10 receiving(e.g., receiving via one or more communication networks 50 the one ormore end user log entries 14 including the data indicating at least oneof the reported aspects from one or more of the end users 4*.

In the same or different implementations, operation 405 may include anoperation 411 for receiving the one or more end user log entriesincluding the data indicating at least one of the reported aspects fromone or more sensors as depicted in FIG. 4 a. For instance, the log entryreceiving module 208 of the computing device 10 receiving the one ormore end user log entries 14 including the data indicating at least oneof the reported aspects from one or more sensors 140.

In the same or different implementations, operation 405 may include anoperation 412 for receiving the one or more end user log entriesincluding the data indicating at least one of the reported aspects fromone or more sensor integrated devices as depicted in FIG. 4 a. Forinstance, the log entry receiving module 208 of the computing device 10receiving the one or more end user log entries 14 including the dataindicating at least one of the reported aspects from one or more sensorintegrated devices 40 (e.g., an automobile, a treadmill, a householdappliance, and so forth).

In various implementations, the operation 402 for determining whetherthe plurality of end users 4* deviated from compliantly executing thetemplate 16 by at least receiving data indicating reported aspects ofthe plurality of end users may include an operation 413 for determiningwhether the plurality of end users deviated from compliantly executingthe template by at least comparing the reported aspects with the one ormore emulatable aspects included in the template as depicted in FIG. 4b. For instance, the deviation determining module 102 including thecomparing module 218 determining whether the plurality of end users4*deviated from compliantly executing the template 16 when the comparingmodule 218 at least compares the reported aspects with the one or moreemulatable aspects included in the template 16.

As further illustrated in FIG. 4 b, operation 413 may include one ormore additional operations in various alternative implementations. Forexample, in some implementations, operation 413 may include an operation414 for identifying which of the one or more emulatable aspects includedin the template were not emulated at all by one or more of the end usersbased on the comparison of the reported aspects with the one or moreemulatable aspects as depicted in FIG. 4 b. For instance, the emulatableaspect identifying module 220 of the computing device 10 identifying(e.g., determining, or finding) which of the one or more emulatableaspects included in the template 16 were not emulated at all by one ormore of the end users 4* based on the comparison of the reported aspectswith the one or more emulatable aspects. In some cases, by making suchidentification, a determination may be made as to which of the one ormore emulatable aspects included in the template 16 may need to bemodified. Note that the phrase “at all” as used above in reference tothe emulatable aspects in the template 16 that were not emulated at allindicate that these emulatable aspects were not even partially emulatedby one or more end users 4* but were, for example, completely ignored ordisregarded.

In some cases, operation 414 may further include an operation 415 foridentifying which of the plurality of end users did not emulate at allthe one or more emulatable aspects included in the template that wereidentified as being not emulated at all by one or more of the end usersas depicted in FIG. 4 b. For instance, the end user identifying module222 of the computing device 10 identifying which of the plurality of endusers 4* did not emulate at all those emulatable aspects included in thetemplate 16 that were identified as being not emulated at all by one ormore of the end users 4*. In some implementations, by making suchidentification, a determination may be made as to whether the template16 should be modified. For example, in some cases, template 16 may bemodified only if a majority of end users 4* or at least a significantportion of the end user 4* were identified as not emulating at all one,some, or all of the one or more emulatable aspects of the template 16.

In various implementations, operation 413 may include an operation 416for identifying which of the one or more emulatable aspects included intemplate were only partially emulated by one or more of the end usersbased on the comparison of the reported aspects with the one or moreemulatable aspects as depicted in FIG. 4 b. For instance, the emulatableaspect identifying module 220 of the computing device 10 identifyingwhich of the one or more emulatable aspects included in template 16 wereonly partially emulated by one or more of the end users 4* based on thecomparison of the reported aspects with the one or more emulatableaspects. In some cases, by making such an identification, adetermination may be made as to which of the one or more emulatableaspects included in the template 16 may need to be modified.

In some implementations, operation 416 may further include an operation417 for identifying which of the plurality of end users only partiallyemulated the one or more emulatable aspects included in the templatethat were identified as being only partially emulated by one or more ofthe end users as depicted in FIG. 4 b. For instance, the end useridentifying module 222 of the computing device 10 identifying which ofthe plurality of end users 4* only partially emulated those emulatableaspects included in the template 16 that were identified as being onlypartially emulated by one or more of the end users 4*. In someimplementations, by making such identification, a determination may bemade as to whether the template 16 should be modified. For example, insome cases template 16 may be modified only if a majority of end users4* or at least a significant portion of the plurality of end users 4*were identified as only partially emulating one, some, or all of the oneor more emulatable aspects of the template 16.

In some implementations, operation 413 may include an operation 418 foridentifying which of the reported aspects of the plurality of end usersrepresent one or more replacement aspects for the one or more emulatableaspects included in the template as depicted in FIG. 4 b. For instance,the reported aspect identifying module 224 of the computing device 10identifying which of the reported aspects of the plurality of end users4* represent one or more replacement aspects for the one or moreemulatable aspects included in the template 16 that may be replaced orrevised when the template 16 is being, for example, modified. Theidentification of one or more replacement aspects from the reportedaspects of the plurality of end users 4* may be based on a number offactors. For example, in some implementations, reported aspects that aredeviations from the one or more emulatable aspects included in thetemplate 16 and that are most commonly executed by the end users 4* maybe identified as replacement aspects. Suppose, for example, template 16included an emulatable aspect that required end users 4* to go joggingfor 30 minutes on the fourth day. However, if most of the non-compliantend users 4* went swimming 20 minutes on the fourth day rather thanjogging, than swimming for 20 minutes may be identified as a replacementaspect.

In same or different implementations, operation 413 may include anoperation 419 for determining whether the plurality of end usersdeviated from compliantly executing the template by at least determiningwhether the plurality of end users did not emulate a plurality ofemulatable aspects included in the template in a particular order asdefined by the template as depicted in FIG. 4 b. For instance, thedeviation determining module 102 including the particular orderdetermining module 226 of the computing device 10 determining whetherthe plurality of end users 4* deviated from compliantly executing thetemplate 16 when the particular order determining module 226 at leastdetermines whether the plurality of end users 4* did not emulate aplurality of emulatable aspects included in the template 16 in aparticular order as defined by the template 16. In other words, if thetemplate 16 includes a plurality of emulatable aspects, and the template16 defines the temporal or specific time order in which the emulatableaspects are to be emulated, than an end user 4* may not have compliantlyexecuted the template 16 if the end user 4* emulates at least some ofthe emulatable aspects in an incorrect order (e.g., incorrect sequence).

In various implementations, operation 419 may further include anoperation 420 for determining whether the plurality of end usersdeviated from compliantly executing the template by at least determiningwhether the plurality of end users did not emulate a plurality ofemulatable aspects included in the template in a particular temporalorder as defined by the template as depicted in FIG. 4 b. For instance,the deviation determining module 102 including the particular orderdetermining module 226 of the computing device 10 determining whetherthe plurality of end users 4* deviated from compliantly executing thetemplate 16 when the particular order determining module 226 at leastdetermines whether the plurality of end users 4* did not emulate aplurality of emulatable aspects included in the template 16 in aparticular temporal order as defined by the template 16.

In some implementations, operation 419 may include an operation 421 fordetermining whether the plurality of end users deviated from compliantlyexecuting the template by at least determining whether the plurality ofend users did not emulate a plurality of emulatable aspects included inthe template in a specific time order as defined by the template asdepicted in FIG. 4 b. For instance, the deviation determining module 102including the particular order determining module 226 of the computingdevice 10 determining whether the plurality of end users 4* deviatedfrom compliantly executing the template 16 when the particular orderdetermining module 226 at least determines whether the plurality of endusers 4* did not emulate a plurality of emulatable aspects included inthe template 16 in a specific time order as defined by the template 16.

Various types of templates 16 may be involved in the deviationdetermining operation 302 of FIG. 3. For example, in someimplementations, the deviation determining operation 302 may include anoperation 422 for determining whether a plurality of end users deviatedfrom compliantly executing a template designed to facilitate theplurality of end users in achieving one or more health or medicaloutcomes as depicted in FIG. 4 c. For instance, the deviationdetermining module 102 of the computing device 10 determining whether aplurality of end users 4* deviated from compliantly executing a template16 designed to facilitate the plurality of end users 4* in achieving oneor more health or medical outcomes (e.g., losing weight, improve resultsof a medical treatment, reduce pain, reduce stress, reduce bloodpressure or blood glucose levels, and so forth).

In some implementations, the deviation determining operation 302 mayinclude an operation 423 for determining whether a plurality of endusers deviated from compliantly executing a template designed tofacilitate the plurality of end users in achieving one or more athleticor gaming outcomes as depicted in FIG. 4 c. For instance, the deviationdetermining module 102 of the computing device 10 determining whether aplurality of end users 4* deviated from compliantly executing a template16 designed to facilitate the plurality of end users 4* in achieving oneor more athletic or gaming outcomes (e.g., win a tennis tournament,lower golf handicap, improve scores on an electronic game, and soforth).

In some implementations, the deviation determining operation 302 mayinclude an operation 424 for determining whether a plurality of endusers deviated from compliantly executing a template designed tofacilitate the plurality of end users in achieving one or moreoccupational outcomes as depicted in FIG. 4 c. For instance, thedeviation determining module 102 of the computing device 10 determiningwhether a plurality of end users 4* deviated from compliantly executinga template 16 designed to facilitate the plurality of end users 4* inachieving one or more occupational outcomes (e.g., be promoted, developbusiness network, complete a project, and so forth).

In some implementations, the deviation determining operation 302 mayinclude an operation 425 for determining whether a plurality of endusers deviated from compliantly executing a template designed tofacilitate the plurality of end users in achieving one or more social orleisure outcomes as depicted in FIG. 4 c. For instance, the deviationdetermining module 102 of the computing device 10 determining whether aplurality of end users 4* deviated from compliantly executing a template16 designed to facilitate the plurality of end users 4* in achieving oneor more social or leisure outcomes (e.g., develop more friendships,achieve certain social status, be invited to join a particular socialclub, and so forth).

In some implementations, the deviation determining operation 302 mayinclude an operation 426 for determining whether a plurality of endusers deviated from compliantly executing a template designed tofacilitate the plurality of end users in achieving one or more sexualintimacy outcomes as depicted in FIG. 4 c. For instance, the deviationdetermining module 102 of the computing device 10 determining whether aplurality of end users 4* deviated from compliantly executing a template16 designed to facilitate the plurality of end users 4* in achieving oneor more sexual intimacy outcomes (e.g., increase the frequency of sexualencounters).

In some implementations, the deviation determining operation 302 mayinclude an operation 427 for determining whether a plurality of endusers deviated from compliantly executing a template designed tofacilitate the plurality of end users in achieving one or more academicor intellectual outcomes as depicted in FIG. 4 c. For instance, thedeviation determining module 102 of the computing device 10 determiningwhether a plurality of end users 4* deviated from compliantly executinga template 16 designed to facilitate the plurality of end users 4* inachieving one or more academic or intellectual outcomes (e.g.,understanding particular concepts introduced in a book, accepted forenrollment at a particular University, and so forth).

In some implementations, the deviation determining operation 302 mayinclude an operation 428 for determining whether a plurality of endusers deviated from compliantly executing a template designed tofacilitate the plurality of end users in achieving one or more spiritualor religious outcomes as depicted in FIG. 4 c. For instance, thedeviation determining module 102 of the computing device 10 determiningwhether a plurality of end users 4* deviated from compliantly executinga template 16 designed to facilitate the plurality of end users 4* inachieving one or more spiritual or religious outcomes (e.g., achievespiritual harmony, acceptance to a particular church or religion, and soforth).

In some implementations, the deviation determining operation 302 mayinclude an operation 429 for determining whether a plurality of endusers deviated from compliantly executing a template designed tofacilitate the plurality of end users in achieving one or more userstate outcomes as depicted in FIG. 4 c. For instance, the deviationdetermining module 102 of the computing device 10 determining whether aplurality of end users 4* deviated from compliantly executing a template16 designed to facilitate the plurality of end users 4* in achieving oneor more user state outcomes (e.g., achieve certain subjective userstates such as being “happy” or “content,” achieve certain social statessuch as being married, and so forth).

Referring back to FIG. 3, the template modifying operation 304 may beimplemented in a number of different ways in various alternativeimplementations. For example, in some implementations, the templatemodifying operation 304 of FIG. 3 may include an operation 530 formodifying the template by modifying at least one of the one or moreemulatable aspects included in the template as depicted in FIG. 5 a. Forinstance, the template modifying module 104 including the emulatableaspect modifying module 230 of the computing device 10 modifying thetemplate 16 when the emulatable aspect modifying module 230 modifies atleast one of the one or more emulatable aspects included in the template16.

There are a number of ways in which an emulatable aspect that may beincluded in a template 16 may be modified. For example, in someimplementations, operation 530 may include an operation 531 formodifying the at least one of the one or more emulatable aspectsincluded in the template by revising the at least one of the one or moreemulatable aspects included in the template as depicted in FIG. 5 a. Forinstance, the emulatable aspect modifying module 230 including theemulatable aspect revising module 232 modifying the at least one of theone or more emulatable aspects included in the template 16 when theemulatable aspect revising module 232 revises the at least one of theone or more emulatable aspects included in the template 16.

In the same or different implementations, operation 530 may include anoperation 532 for modifying the at least one of the one or moreemulatable aspects included in the template by replacing the at leastone of the one or more emulatable aspects included in the template withat least one replacement emulatable aspect as depicted in FIG. 5 a. Forinstance, the emulatable aspect modifying module 230 including theemulatable aspect replacing module 234 modifying the at least one of theone or more emulatable aspects included in the template 16 when theemulatable aspect replacing module 234 replaces the at least one of theone or more emulatable aspects included in the template 16 with at leastone replacement emulatable aspect.

In the same or different implementations, operation 530 may include anoperation 533 for modifying the at least one of the one or moreemulatable aspects included in the template by deleting the at least oneof the one or more emulatable aspects included in the template asdepicted in FIG. 5 a. For instance, the emulatable aspect modifyingmodule 230 including the emulatable aspect deleting module 236 modifyingthe at least one of the one or more emulatable aspects included in thetemplate 16 when the emulatable aspect deleting module 236 deletes theat least one of the one or more emulatable aspects included in thetemplate 16. Note that a deletion of an emulatable aspect may bepossible when, for example, it is determined that end users 4* whenexecuting the template 16 may have skipped emulating a particularemulatable aspect included in the template 16 without compromising theoutcome (e.g., achieving the target outcome).

In various implementations, the template modifying operation 304 mayinclude an operation 534 for modifying the template by adding to thetemplate at least one additional emulatable aspect as depicted in FIG. 5a. For instance, the template modifying module 104 including theemulatable aspect adding module 238 of the computing device 10 modifyingthe template 16 when the emulatable aspect adding module 238 adds to thetemplate 16 at least one additional emulatable aspect. This may bepossible, for example, when end users 4* deviate from the compliantexecution of the template 16 that results in the need for an additionalemulatable aspect in order to achieve the one or more target outcomes.For example, if end users 4* deviate from the compliant execution of thetemplate 16 by swimming for only 20 minutes rather than swimming for 40minutes as required by the template 16, then the template 16 may bemodified to include an additional emulatable aspect for another 20minute swim.

In some implementations, operation 534 may further include an operation535 for adding to the template the at least one additional emulatableaspect by defining in the template one or more relationships between theat least one additional emulatable aspect and the one or more emulatableaspects included in the template as depicted in FIG. 5 a. For instance,the emulatable aspect adding module 238 including the relationshipdefining module 240 of the computing device 10 adding to the template 16the at least one additional emulatable aspect including defining by therelationship defining module 240 in the template 16 one or morerelationships (e.g., temporal or specific time relationships) betweenthe at least one additional emulatable aspect and the one or moreemulatable aspects included in the template 16.

In the same or different implementations, the template modifyingoperation 304 may include an operation 536 for modifying the template bymodifying one or more relationships between a plurality of emulatableaspects included in the template as depicted in FIG. 5 a. For instance,the template modifying module 104 including the relationship modifyingmodule 242 modifying the template 16 including modifying by therelationship modifying module 242 one or more relationships between aplurality of emulatable aspects included in the template 16.

In various implementations, operation 536 may further include anoperation 537 for modifying the template by modifying one or moretemporal relationships between the plurality of emulatable aspectsincluded in the template as depicted in FIG. 5 a. For instance, thetemplate modifying module 104 including the relationship modifyingmodule 242 modifying the template 16 including modifying by therelationship modifying module 242 one or more temporal relationshipsbetween a plurality of emulatable aspects included in the template 16.

In some implementations, operation 536 may include an operation 538 formodifying the template by modifying one or more specific timerelationships between the plurality of emulatable aspects included inthe template as depicted in FIG. 5 a. For instance, the templatemodifying module 104 including the relationship modifying module 242modifying the template 16 including modifying by the relationshipmodifying module 242 one or more specific time relationships between aplurality of emulatable aspects included in the template 16.

In the same or different implementations, the template modifyingoperation 304 may include an operation 539 for modifying the template toinclude at least one plausible emulatable aspect that has beendetermined to have been successfully emulated by at least a portion ofthe plurality of end users as depicted in FIG. 5 a. For instance, thetemplate modifying module 104 of the computing device 10 modifying thetemplate 16 to include at least one plausible emulatable aspect (e.g., aplausible modified emulatable aspect, a plausible replacement emulatableaspect, a plausible additional emulatable aspect, and so forth) that hasbeen determined to have been successfully emulated by at least a portionof the plurality of end users 4*.

In some implementations, operation 539 for presenting one or morerecommendations may include an operation 540 for modifying the templateto include at least one plausible emulatable aspect that has beendetermined to have been successfully emulated by a majority of theplurality of end users as depicted in FIG. 5 a. For instance, thetemplate modifying module 104 of the computing device 10 modifying thetemplate 16 to include at least one plausible emulatable aspect (e.g., aplausible modified emulatable aspect, a plausible replacement emulatableaspect, a plausible additional emulatable aspect, and so forth) that hasbeen determined to have been successfully emulated by a majority of theplurality of end users 4*.

In various implementations, the one or more actions executed in thetemplate modifying operation 304 of FIG. 3 may include an operation 541for modifying the template to include at least one emulatable aspectthat was provided by at least analyzing a plurality of reported aspectsof the plurality of end users, the plurality of reported aspectsdeviating from at least one of the one or more emulatable aspectsincluded in the template as depicted in FIG. 5 b. For instance, thetemplate modifying module 104 including the reported aspect analyzingmodule 243 modifying the template 16 to include at least one emulatableaspect that was provided by the reported aspect analyzing module 243 atleast analyzing a plurality of reported aspects (e.g., as acquiredthrough end user log entries 14) of the plurality of end users 4*, theplurality of reported aspects deviating from at least one of the one ormore emulatable aspects included in the template 16.

Operation 541 may, in turn, include an operation 542 for modifying thetemplate to include at least one mean value emulatable aspect that wasat least provided by developing a mean value for a plurality of reportedaspects of the plurality of end users, the reported aspectscorresponding to and deviating from at least one of the one or moreemulatable aspects included in the template as depicted in FIG. 5 b. Forinstance, the template modifying module 104 including the mean valueemulatable aspect developing module 246 of the computing device 10modifying the template 16 to include at least one mean value emulatableaspect that was at least provided by the mean value emulatable aspectdeveloping module 246 by developing a mean value for a plurality ofreported aspects of the plurality of end users 4*, the reported aspectscorresponding to and deviating from at least one of the one or moreemulatable aspects included in the template 16. For example, suppose thetemplate 16 included an emulatable aspect that required the end users 4*to study a particular reference book for one hour. However, if the endusers 4* in executing the template 16 reported that they studied forless than or more than one hour as required by the template 16, then themean value emulatable aspect, in this case, would be the mean reportedaspects of the end users 4*.

In some implementations, operation 541 may include an operation 543 formodifying the template to include at least one average value emulatableaspect that was at least provided by developing an average value for aplurality of reported aspects of the plurality of end users, theplurality of reported aspects corresponding to and deviating from atleast one of the one or more emulatable aspects included in the templateas depicted in FIG. 5 b. For instance, the template modifying module 104including the average value emulatable aspect developing module 248 ofthe computing device 10 modifying the template 16 to include at leastone average value emulatable aspect that was at least provided by theaverage value emulatable aspect developing module 248 by developing anaverage value for a plurality of reported aspects of the plurality ofend users 4*, the plurality of reported aspects corresponding to anddeviating from at least one of the one or more emulatable aspectsincluded in the template 16.

In some implementations, operation 541 may include an operation 544 formodifying the template to include at least one emulatable aspect thatwas provided by determining from a plurality of reported aspects of theplurality of end users an end user aspect that was reported more thanonce, the plurality of reported aspects corresponding to and deviatingfrom at least one of the one or more emulatable aspects included in thetemplate as depicted in FIG. 5 b. For instance, the template modifyingmodule 104 including the reported aspect analyzing module 243 configuredto modify the template 16 to include at least one emulatable aspect thatwas provided by the reported aspect analyzing module 243 when thereported aspect analyzing module 243 determines from a plurality ofreported aspects of the plurality of end users an end user aspect (e.g.,jogging for 40 minutes instead of one hour as required by the template16) that was reported more than once, the plurality of reported aspectscorresponding to and deviating from at least one of the one or moreemulatable aspects included in the template 16. In other words, lookingat the reported aspects of end users 4* and look for deviations thatoccurred repeatedly. Such deviation may then be used in order to modifythe template by, for example, modifying, substituting, or adding anemulatable aspect into the template 16 that corresponds to the repeateddeviations.

In some implementations, operation 544 may further include an operation545 for modifying the template to include at least one emulatable aspectthat was provided by determining a reported aspect that was mostcommonly reported aspect from a plurality of reported aspects of theplurality of end users, the plurality of reported aspects correspondingto and deviating from at least one of the one or more emulatable aspectsincluded in the template as depicted in FIG. 5 b. For instance, thetemplate modifying module 104 including the reported aspect analyzingmodule 243 configured to modify the template 16 to include at least oneemulatable aspect that was provided by the reported aspect analyzingmodule 243 when the reported aspect analyzing module 243 determines areported aspect that was most commonly reported aspect from a pluralityof reported aspects (e.g., as indicated by end user log entries 14) ofthe plurality of end users 4*, the plurality of reported aspectscorresponding to and deviating from at least one of the one or moreemulatable aspects included in the template. In other words, to modifythe template by including into the template 16 (e.g., by substitution,modification, or addition), an emulatable aspect corresponding to themost commonly occurring deviation.

In the same or different implementations, the template modifyingoperation 304 of FIG. 3 may include an operation 546 for modifying thetemplate in response to determining that one or more of the end usersdid not emulate at all at least one of the one or more emulatableaspects included in the template as depicted in FIG. 5 b. For instance,the template modifying module 104 of the computing device 10 modifyingthe template 16 in response to determining that one or more of the endusers 4* did not emulate at all at least one of the one or moreemulatable aspects included in the template 16.

In the same or different implementations, the template modifyingoperation 304 may include an operation 547 for modifying the template inresponse to determining that one or more of the end users only partiallyemulated at least one of the one or more emulatable aspects included inthe template as depicted in FIG. 5 b. For instance, the templatemodifying module 104 of the computing device 10 modifying the template16 in response to determining that one or more of the end users 4* onlypartially emulated at least one of the one or more emulatable aspectsincluded in the template 16.

In the same or different implementations, the template modifyingoperation 304 may include an operation 548 for modifying the template toinclude at least one emulatable aspect that relate to at least oneemulatable behavior as depicted in FIG. 5 b. For instance, the templatemodifying module 104 of the computing device 10 modifying the template16 to include (e.g., by revising, replacing, or adding) at least oneemulatable aspect that relate to at least one emulatable behavior (e.g.,dietary behavior, social behavior, and so forth).

In some implementations, operation 548 may include an operation 549 formodifying the template to include at least one emulatable aspect thatrelate to at least one emulatable user activity as depicted in FIG. 5 b.For instance, the template modifying module 104 of the computing device10 modifying the template 16 to include (e.g., by revising, replacing,or adding) at least one emulatable aspect that relate to at least oneemulatable user activity (e.g., walking, resting, riding a bicycle,attending church, and so forth).

In the same or different implementations, operation 548 may include anoperation 550 for modifying the template to include at least oneemulatable aspect that relate to at least one emulatable user attitudeas depicted in FIG. 5 b. For instance, the template modifying module 104of the computing device 10 modifying the template 16 to include (e.g.,by revising, replacing, or adding) at least one emulatable aspect thatrelate to at least one emulatable user attitude (e.g., distaste,positive or negative attitude, and so forth).

In the same or different implementations, operation 548 may include anoperation 551 for modifying the template to include at least oneemulatable aspect that relate to at least one emulatable user conduct asdepicted in FIG. 5 b. For instance, the template modifying module 104 ofthe computing device 10 modifying the template 16 to include (e.g., byrevising, replacing, or adding) at least one emulatable aspect thatrelate to at least one emulatable user conduct (e.g., treatingsubordinates as equals, being evasive, and so forth).

In some implementations, the template modifying operation 304 of FIG. 3may include an operation 552 for modifying the template to include atleast one emulatable aspect that relate to at least one emulatable userbelief as depicted in FIG. 5 c. For instance, the template modifyingmodule 104 of the computing device 10 modifying the template 16 toinclude (e.g., by revising, replacing, or adding) at least oneemulatable aspect that relate to at least one emulatable user belief(e.g., religious belief, spiritual belief, dietary belief, and soforth).

In the same or different implementations, the template modifyingoperation 304 of FIG. 3 may include an operation 553 for modifying thetemplate to include at least one emulatable aspect that relate to atleast one emulatable user state as depicted in FIG. 5 c. For instance,the template modifying module 104 of the computing device 10 modifyingthe template 16 to include (e.g., by revising, replacing, or adding) atleast one emulatable aspect that relate to at least one emulatable userstate (e.g., subjective user states such as being happy, being alert, orbeing prepared, objective user states such as being married, beingunderweight, being employed, and so forth).

In the same or different implementations, the template modifyingoperation 304 of FIG. 3 may include an operation 554 for modifying thetemplate to include at least one emulatable aspect that relate to atleast one user physical characteristic as depicted in FIG. 5 c. Forinstance, the template modifying module 104 of the computing device 10modifying the template 16 to include (e.g., by revising, replacing, oradding) at least one emulatable aspect that relate to at least one userphysical characteristic (e.g., low blood pressure, hair color, low bodyfat level, and so forth).

In the same or different implementations, the template modifyingoperation 304 of FIG. 3 may include an operation 555 for modifying thetemplate to include at least one emulatable aspect that relate to atleast one user external event as depicted in FIG. 5 c. For instance, thetemplate modifying module 104 of the computing device 10 modifying thetemplate 16 to include (e.g., by revising, replacing, or adding) atleast one emulatable aspect that relate to at least one user externalevent (e.g., local atmospheric conditions, drinking water quality, roadtraffic, and so forth).

In the same or different implementations, the template modifyingoperation 304 of FIG. 3 may include an operation 556 for modifying thetemplate based, at least in part, on determining that the plurality ofend users deviated from the compliant execution of the template, theplurality of end users determined to have achieved the one or moretarget outcomes even though the template was not compliantly executed bythe plurality of end users as depicted in FIG. 5 c. For instance, thetemplate modifying module 104 of the computing device 10 modifying thetemplate 16 based, at least in part, on determining that the pluralityof end users 4* deviated from the compliant execution of the template16, the plurality of end users 4* determined to have achieved the one ormore target outcomes even though the template 16 was not compliantlyexecuted by the plurality of end users 4*.

Referring to FIG. 6 illustrating another operational flow 600 inaccordance with various embodiments. Operational flow 600 includescertain operations that mirror the operations included in theoperational flow 300 of FIG. 3. These operations include a deviationdetermining operation 602 and a template modifying operation 604 thatcorresponds to and mirror the deviation determining operation 302 andthe template modifying operation 304, respectively, of FIG. 3.

In addition, operational flow 600 includes a modified templatepresenting operation 606 for presenting the modified template asdepicted in FIG. 6. For instance, the modified template presentingmodule 106 of the computing device 10 presenting the modified template18 resulting from the template modifying operation 604.

In some implementations, the modified template presenting operation 606of FIG. 6 may include an operation 758 for transmitting the modifiedtemplate via one or more communication networks as depicted in FIG. 7.For instance, the network transmitting module 130 (see FIG. 1 b) of thecomputing device 10 transmitting the modified template 18 via one ormore communication networks 50.

In the same or different implementations, the modified templatepresenting operation 606 of FIG. 6 may include an operation 759 forpresenting the modified template to at least one of the plurality of endusers as depicted in FIG. 7. For instance, the modified templatepresenting module 106 of the computing device 10 presenting the modifiedtemplate 18 to at least one of the plurality of end users 4*.

In the same or different implementations, the modified templatepresenting operation 606 of FIG. 6 may include an operation 760 forpresenting the modified template to one or more third parties asdepicted in FIG. 7. For instance, the modified template presentingmodule 106 of the computing device 10 presenting the modified template18 to one or more third parties 6 (e.g., network servers 60, contentproviders, and so forth).

In the same or different implementations, the modified templatepresenting operation 606 of FIG. 6 may include an operation 761 forpresenting the modified template to one or more other end users asdepicted in FIG. 7. For instance, the modified template presentingmodule 106 of the computing device 10 presenting the modified template18 to one or more other end users who may have yet to execute thetemplate 16 or the modified template 18.

Turning now to FIG. 8, which is a high-level block diagram illustratinga particular implementation of the computing device 10 of FIG. 1 b. Asillustrated, the computing device 10 may include a processor 802 (e.g.,microprocessor, controller, and so forth) coupled to storage medium 806(e.g., volatile or non-volatile memory). The storage medium 806 maystore computer readable instructions 804 (e.g., computer programproduct). The processor 802, in various implementations, may execute thecomputer readable instructions 804 in order to execute one or moreoperations described above and as illustrated in FIGS. 3, 4 a, 4 b, 4 c,5 a, 5 b, 5 c, 6, and 7.

For example, the processor 802 may execute the computer readableinstructions 804 in order to determine whether a plurality of end users4* deviated from compliantly executing a template 16 designed tofacilitate the plurality of end users 4* in achieving one or more targetoutcomes when one or more emulatable aspects included in the template 16are emulated by the plurality of end users 4*, the one or moreemulatable aspects being based on one or more relevant reported aspectsof one or more source users 2* that were deemed to have been relevant toachieving the one or more target outcomes; and/or to modify the template16 based, at least in part, on determining that the plurality of endusers 4* deviated from compliantly executing the template 16 asillustrated by the operational flow 300 of FIG. 3.

Those having skill in the art will recognize that the state of the arthas progressed to the point where there is little distinction leftbetween hardware and software implementations of aspects of systems; theuse of hardware or software is generally (but not always, in that incertain contexts the choice between hardware and software can becomesignificant) a design choice representing cost vs. efficiency tradeoffs.Those having skill in the art will appreciate that there are variousvehicles by which processes and/or systems and/or other technologiesdescribed herein can be effected (e.g., hardware, software, and/orfirmware), and that the preferred vehicle will vary with the context inwhich the processes and/or systems and/or other technologies aredeployed. For example, if an implementer determines that speed andaccuracy are paramount, the implementer may opt for a mainly hardwareand/or firmware vehicle; alternatively, if flexibility is paramount, theimplementer may opt for a mainly software implementation; or, yet againalternatively, the implementer may opt for some combination of hardware,software, and/or firmware. Hence, there are several possible vehicles bywhich the processes and/or devices and/or other technologies describedherein may be effected, none of which is inherently superior to theother in that any vehicle to be utilized is a choice dependent upon thecontext in which the vehicle will be deployed and the specific concerns(e.g., speed, flexibility, or predictability) of the implementer, any ofwhich may vary. Those skilled in the art will recognize that opticalaspects of implementations will typically employ optically-orientedhardware, software, and or firmware.

The foregoing detailed description has set forth various embodiments ofthe devices and/or processes via the use of block diagrams, flowcharts,and/or examples. Insofar as such block diagrams, flowcharts, and/orexamples contain one or more functions and/or operations, it will beunderstood by those within the art that each function and/or operationwithin such block diagrams, flowcharts, or examples can be implemented,individually and/or collectively, by a wide range of hardware, software,firmware, or virtually any combination thereof. In one embodiment,several portions of the subject matter described herein may beimplemented via Application Specific Integrated Circuitry (ASICs), FieldProgrammable Gate Arrays (FPGAs), digital signal processors (DSPs), orother integrated formats. However, those skilled in the art willrecognize that some aspects of the embodiments disclosed herein, inwhole or in part, can be equivalently implemented in integratedcircuitry, as one or more computer programs running on one or morecomputers (e.g., as one or more programs running on one or more computersystems), as one or more programs running on one or more processors(e.g., as one or more programs running on one or more microprocessors),as firmware, or as virtually any combination thereof, and that designingthe circuitry and/or writing the code for the software and or firmwarewould be well within the skill of one of skill in the art in light ofthis disclosure. In addition, those skilled in the art will appreciatethat the mechanisms of the subject matter described herein are capableof being distributed as a program product in a variety of forms, andthat an illustrative embodiment of the subject matter described hereinapplies regardless of the particular type of signal bearing medium usedto actually carry out the distribution. Examples of a signal bearingmedium include, but are not limited to, the following: a recordable typemedium such as a floppy disk, a hard disk drive, a Compact Disc (CD), aDigital Video Disk (DVD), a digital tape, a computer memory, etc.; and atransmission type medium such as a digital and/or an analogcommunication medium (e.g., a fiber optic cable, a waveguide, a wiredcommunications link, a wireless communication link, etc.).

In a general sense, those skilled in the art will recognize that thevarious aspects described herein which can be implemented, individuallyand/or collectively, by a wide range of hardware, software, firmware, orany combination thereof can be viewed as being composed of various typesof “electrical circuitry.” Consequently, as used herein “electricalcircuitry” includes, but is not limited to, electrical circuitry havingat least one discrete electrical circuit, electrical circuitry having atleast one integrated circuit, electrical circuitry having at least oneapplication specific integrated circuit, electrical circuitry forming ageneral purpose computing device configured by a computer program (e.g.,a general purpose computer configured by a computer program which atleast partially carries out processes and/or devices described herein,or a microprocessor configured by a computer program which at leastpartially carries out processes and/or devices described herein),electrical circuitry forming a memory device (e.g., forms of randomaccess memory), and/or electrical circuitry forming a communicationsdevice (e.g., a modem, communications switch, or optical-electricalequipment). Those having skill in the art will recognize that thesubject matter described herein may be implemented in an analog ordigital fashion or some combination thereof.

Those having skill in the art will recognize that it is common withinthe art to describe devices and/or processes in the fashion set forthherein, and thereafter use engineering practices to integrate suchdescribed devices and/or processes into data processing systems. Thatis, at least a portion of the devices and/or processes described hereincan be integrated into a data processing system via a reasonable amountof experimentation. Those having skill in the art will recognize that atypical data processing system generally includes one or more of asystem unit housing, a video display device, a memory such as volatileand non-volatile memory, processors such as microprocessors and digitalsignal processors, computational entities such as operating systems,drivers, graphical user interfaces, and applications programs, one ormore interaction devices, such as a touch pad or screen, and/or controlsystems including feedback loops and control motors (e.g., feedback forsensing position and/or velocity; control motors for moving and/oradjusting components and/or quantities). A typical data processingsystem may be implemented utilizing any suitable commercially availablecomponents, such as those typically found in datacomputing/communication and/or network computing/communication systems.

The herein described subject matter sometimes illustrates differentcomponents contained within, or connected with, different othercomponents. It is to be understood that such depicted architectures aremerely exemplary, and that in fact many other architectures can beimplemented which achieve the same functionality. In a conceptual sense,any arrangement of components to achieve the same functionality iseffectively “associated” such that the desired functionality isachieved. Hence, any two components herein combined to achieve aparticular functionality can be seen as “associated with” each othersuch that the desired functionality is achieved, irrespective ofarchitectures or intermedial components. Likewise, any two components soassociated can also be viewed as being “operably connected”, or“operably coupled”, to each other to achieve the desired functionality,and any two components capable of being so associated can also be viewedas being “operably couplable”, to each other to achieve the desiredfunctionality. Specific examples of operably couplable include but arenot limited to physically mateable and/or physically interactingcomponents and/or wirelessly interactable and/or wirelessly interactingcomponents and/or logically interacting and/or logically interactablecomponents.

While particular aspects of the present subject matter described hereinhave been shown and described, it will be apparent to those skilled inthe art that, based upon the teachings herein, changes and modificationsmay be made without departing from the subject matter described hereinand its broader aspects and, therefore, the appended claims are toencompass within their scope all such changes and modifications as arewithin the true spirit and scope of the subject matter described herein.Furthermore, it is to be understood that the invention is defined by theappended claims.

It will be understood by those within the art that, in general, termsused herein, and especially in the appended claims (e.g., bodies of theappended claims) are generally intended as “open” terms (e.g., the term“including” should be interpreted as “including but not limited to,” theterm “having” should be interpreted as “having at least,” the term“includes” should be interpreted as “includes but is not limited to,”etc.). It will be further understood by those within the art that if aspecific number of an introduced claim recitation is intended, such anintent will be explicitly recited in the claim, and in the absence ofsuch recitation no such intent is present. For example, as an aid tounderstanding, the following appended claims may contain usage of theintroductory phrases “at least one” and “one or more” to introduce claimrecitations. However, the use of such phrases should not be construed toimply that the introduction of a claim recitation by the indefinitearticles “a” or “an” limits any particular claim containing suchintroduced claim recitation to inventions containing only one suchrecitation, even when the same claim includes the introductory phrases“one or more” or “at least one” and indefinite articles such as “a” or“an” (e.g., “a” and/or “an” should typically be interpreted to mean “atleast one” or “one or more”); the same holds true for the use ofdefinite articles used to introduce claim recitations.

In addition, even if a specific number of an introduced claim recitationis explicitly recited, those skilled in the art will recognize that suchrecitation should typically be interpreted to mean at least the recitednumber (e.g., the bare recitation of “two recitations,” without othermodifiers, typically means at least two recitations, or two or morerecitations). Furthermore, in those instances where a conventionanalogous to “at least one of A, B, and C, etc.” is used, in generalsuch a construction is intended in the sense one having skill in the artwould understand the convention (e.g., “a system having at least one ofA, B, and C” would include but not be limited to systems that have Aalone, B alone, C alone, A and B together, A and C together, B and Ctogether, and/or A, B, and C together, etc.).

In those instances where a convention analogous to “at least one of A,B, or C, etc.” is used, in general such a construction is intended inthe sense one having skill in the art would understand the convention(e.g., “a system having at least one of A, B, or C” would include butnot be limited to systems that have A alone, B alone, C alone, A and Btogether, A and C together, B and C together, and/or A, B, and Ctogether, etc.). It will be further understood by those within the artthat virtually any disjunctive word and/or phrase presenting two or morealternative terms, whether in the description, claims, or drawings,should be understood to contemplate the possibilities of including oneof the terms, either of the terms, or both terms. For example, thephrase “A or B” will be understood to include the possibilities of “A”or “B” or “A and B.”

1. A system, comprising: a deviation determining module configured todetermine whether a plurality of end users deviated from compliantlyexecuting a template designed to facilitate the plurality of end usersin achieving one or more target outcomes when one or more emulatableaspects included in the template are emulated by the plurality of endusers, the one or more emulatable aspects being based on one or morerelevant reported aspects of one or more source users that were deemedto have been relevant to achieving the one or more target outcomes; anda template modifying module configured to modify the template based, atleast in part, on determining that the plurality of end users deviatedfrom compliantly executing the template, wherein said template modifyingmodule comprises: a template modifying module configured to modify thetemplate to include at least one plausible emulatable aspect that hasbeen determined to have been successfully emulated by at least a portionof the plurality of end users.
 2. The system of claim 1, wherein saiddeviation determining module comprises: a reported aspect data receivingmodule configured to at least receive data indicating reported aspectsof the plurality of end users to facilitate the deviation determiningmodule to determine whether the plurality of end users deviated fromcompliantly executing the template.
 3. The system of claim 2, whereinsaid reported aspect data receiving module comprises: a log entryreceiving module configured to receive data indicating at least one ofthe reported aspects via one or more end user log entries.
 4. The systemof claim 3, wherein said log entry receiving module comprises: a socialnetworking entry receiving module configured to receive, via one or moresocial networking entries, the data indicating at least one of thereported aspects.
 5. The system of claim 4, wherein social networkingentry receiving module comprises: a blog entry receiving moduleconfigured to receive, via one or more blog entries, the data indicatingat least one of the reported aspects.
 6. The system of claim 4, whereinsocial networking entry receiving module comprises: a status reportreceiving module configured to receive, via one or more status reports,the data indicating at least one of the reported aspects.
 7. The systemof claim 3, wherein said log entry receiving module comprises: a journalentry receiving module configured to receive, via one or more journalentries, the data indicating at least one of the reported aspects. 8.The system of claim 3, wherein said log entry receiving modulecomprises: a log entry receiving module configured to receive the one ormore end user log entries from one or more sensors.
 9. The system ofclaim 3, wherein said log entry receiving module comprises: a log entryreceiving module configured to receive the one or more end user logentries from one or more sensor integrated devices.
 10. The system ofclaim 2, wherein said reported aspect data receiving module comprises: acomparing module configured to compare the reported aspects with the oneor more emulatable aspects included in the template.
 11. The system ofclaim 10, wherein said deviation determining module comprises: anemulatable aspect identifying module configured to identify, based onthe comparison of the reported aspects with the one or more emulatableaspects, which of the one or more emulatable aspects included in thetemplate were not emulated at all by one or more of the end users. 12.The system of claim 11, wherein said deviation determining modulecomprises: an end user identifying module configured to identify whichof the plurality of end users did not emulate at all the one or moreemulatable aspects included in the template that were identified by theemulatable aspect identifying module as being not emulated at all by oneor more of the end users.
 13. The system of claim 10, wherein saiddeviation determining module comprises: an emulatable aspect identifyingmodule configured to identify, based on the comparison of the reportedaspects with the one or more emulatable aspects, which of the one ormore emulatable aspects included in template were only partiallyemulated by one or more of the end users.
 14. The system of claim 13,wherein said deviation determining module comprises: an end useridentifying module configured to identify which of the plurality of endusers only partially emulated the one or more emulatable aspectsincluded in the template that were identified by the emulatable aspectidentifying module as being only partially emulated by one or more ofthe end users.
 15. The system of claim 10, wherein said deviationdetermining module comprises: a reported aspect identifying moduleconfigured to identify which of the reported aspects represent one ormore replacement aspects for one or more emulatable aspects included inthe template.
 16. The system of claim 10, wherein said deviationdetermining module comprises: a particular order determining moduleconfigured to determine whether the plurality of end users did notemulate a plurality of emulatable aspects included in the template in aparticular order as defined by the template, the determination ofwhether the plurality of end users did not emulate the plurality ofemulatable aspects included in the template in a particular order tofacilitate the deviation determining module in determining whether theplurality of end users deviated from compliantly executing the template.17. The system of claim 16, wherein said particular order determiningmodule comprises: an end user identifying module configured to determinewhether the plurality of end users did not emulate a plurality ofemulatable aspects included in the template in a particular temporalorder as defined by the template, the determination of whether theplurality of end users did not emulate the plurality of emulatableaspects included in the template in a particular temporal order tofacilitate the deviation determining module in determining whether theplurality of end users deviated from compliantly executing the template.18. The system of claim 16, wherein said particular order determiningmodule comprises: a particular order determining module configured todetermine whether the plurality of end users did not emulate a pluralityof emulatable aspects included in the template in a specific time orderas defined by the template, the determination of whether the pluralityof end users did not emulate the plurality of emulatable aspectsincluded in the template in a specific time order to facilitate thedeviation determining module in determining whether the plurality of endusers deviated from compliantly executing the template.
 19. The systemof claim 1, wherein said template modifying module comprises: anemulatable aspect modifying module configured to modify at least one ofthe one or more emulatable aspects included in the template.
 20. Thesystem of claim 19, wherein said emulatable aspect modifying modulecomprises: an emulatable aspect revising module configured to revise theat least one of the one or more emulatable aspects included in thetemplate.
 21. The system of claim 19, wherein said emulatable aspectmodifying module comprises: an emulatable aspect replacing moduleconfigured to replace the at least one of the one or more emulatableaspects included in the template with at least one replacementemulatable aspect.
 22. The system of claim 19, wherein said emulatableaspect modifying module comprises: an emulatable aspect deleting moduleconfigured to delete the at least one of the one or more emulatableaspects included in the template.
 23. The system of claim 1, whereinsaid template modifying module comprises: an emulatable aspect addingmodule configured to add to the template at least one additionalemulatable aspect.
 24. The system of claim 23, wherein said emulatableaspect adding module comprises: a relationship defining moduleconfigured to define in the template one or more relationships betweenthe at least one additional emulatable aspect and the one or moreemulatable aspects included in the template.
 25. The system of claim 1,wherein said template modifying module comprises: a relationshipmodifying module configured to modify one or more relationships betweena plurality of emulatable aspects included in the template.
 26. Thesystem of claim 25, wherein said relationship modifying modulecomprises: a relationship modifying module configured to modify one ormore temporal relationships between the plurality of emulatable aspectsincluded in the template.
 27. The system of claim 25, wherein saidrelationship modifying module comprises: a relationship modifying moduleconfigured to modify one or more specific time relationships between theplurality of emulatable aspects included in the template.
 28. The systemof claim 1, wherein said template modifying module comprises: a templatemodifying module configured to modify the template to include at leastone plausible emulatable aspect that has been determined to have beensuccessfully emulated by a majority of the plurality of end users. 29.The system of claim 1, wherein said template modifying module comprises:a reported aspect analyzing module configured analyze a plurality ofreported aspects of the plurality of end users, the plurality ofreported aspects deviating from at least one of the one or moreemulatable aspects included in the template.
 30. The system of claim 29,wherein said reported aspect analyzing module comprises: a mean valueemulatable aspect developing module configured to provide at least onemean value emulatable aspect that is at least partially provided bydeveloping a mean value for a plurality of reported aspects of theplurality of end users, the reported aspects corresponding to anddeviating from at least one of the one or more emulatable aspectsincluded in the template, the template to be modified by including themean value emulatable aspect in the template.
 31. The system of claim29, wherein said reported aspect analyzing module comprises: an averagevalue emulatable aspect developing module configured to provide at leastone average value emulatable aspect that was at least partially providedby developing an average value for a plurality of reported aspects ofthe plurality of end users, the plurality of reported aspectscorresponding to and deviating from at least one of the one or moreemulatable aspects included in the template, the template to be modifiedby including the average value emulatable aspect in the template. 32.The system of claim 29, wherein said reported aspect analyzing modulecomprises: a reported aspect analyzing module configured to provide atleast one emulatable aspect by determining from a plurality of reportedaspects of the plurality of end users an end user aspect that wasreported more than once, the plurality of reported aspects correspondingto and deviating from at least one of the one or more emulatable aspectsincluded in the template, the template to be modified with the at leastone provided emulatable aspect.
 33. The system of claim 32, wherein saidreported aspect analyzing module comprises: a reported aspect analyzingmodule configured to provide at least one emulatable aspect bydetermining a reported aspect that was most commonly reported aspectfrom a plurality of reported aspects of the plurality of end users, theplurality of reported aspects corresponding to and deviating from atleast one of the one or more emulatable aspects included in thetemplate, the template to be modified with the at least one providedemulatable aspect.
 34. The system of claim 1, wherein said templatemodifying module comprises: a template modifying module configured tomodify the template to include at least one emulatable behavior.
 35. Thesystem of claim 34, wherein said template modifying module comprises: atemplate modifying module configured to modify the template to includeat least one emulatable user activity.
 36. The system of claim 34,wherein said template modifying module comprises: a template modifyingmodule configured to modify the template to include at least oneemulatable user attitude.
 37. The system of claim 34, wherein saidtemplate modifying module comprises: a template modifying moduleconfigured to modify the template to include at least one emulatableuser conduct.
 38. The system of claim 1, wherein said template modifyingmodule comprises: a template modifying module configured to modify thetemplate to include at least one emulatable user belief.
 39. The systemof claim 1, wherein said template modifying module comprises: a templatemodifying module configured to modify the template to include at leastone emulatable user state.
 40. The system of claim 1, wherein saidtemplate modifying module comprises: a template modifying moduleconfigured to modify the template to include at least one user physicalcharacteristic.
 41. The system of claim 1, wherein said templatemodifying module comprises: a template modifying module configured tomodify the template to include at least one user external event.
 42. Thesystem of claim 1, wherein said template modifying module comprises: atemplate modifying module configured to modify the template based, atleast in part, on determining that the plurality of end users deviatedfrom the compliant execution of the template, the plurality of end usersdetermined to have achieved the one or more target outcomes even thoughthe template was not compliantly executed by the plurality of end users.43. The system of claim 1, further comprising: a modified templatepresenting module configured to present the modified template.
 44. Asystem, comprising: circuitry for determining whether a plurality of endusers deviated from compliantly executing a template designed tofacilitate the plurality of end users in achieving one or more targetoutcomes when one or more emulatable aspects included in the templateare emulated by the plurality of end users, the one or more emulatableaspects being based on one or more relevant reported aspects of one ormore source users that were deemed to have been relevant to achievingthe one or more target outcomes; and circuitry for modifying thetemplate based, at least in part, on determining that the plurality ofend users deviated from compliantly executing the template, wherein saidcircuitry for modifying the template based, at least in part, ondetermining that the plurality of end users deviated from compliantlyexecuting the template comprises: circuitry for modifying the templateto include at least one plausible emulatable aspect that has beendetermined to have been successfully emulated by at least a portion ofthe plurality of end users.
 45. An article of manufacture, comprising: anon-transitory storage medium bearing: one or more instructions fordetermining whether a plurality of end users deviated from compliantlyexecuting a template designed to facilitate the plurality of end usersin achieving one or more target outcomes when one or more emulatableaspects included in the template are emulated by the plurality of endusers, the one or more emulatable aspects being based on one or morerelevant reported aspects of one or more source users that were deemedto have been relevant to achieving the one or more target outcomes; andone or more instructions for modifying the template based, at least inpart, on determining that the plurality of end users deviated fromcompliantly executing the template, wherein said one or moreinstructions for modifying the template based, at least in part, ondetermining that the plurality of end users deviated from compliantlyexecuting the template comprises: one or more instructions for modifyingthe template to include at least one plausible emulatable aspect thathas been determined to have been successfully emulated by at least aportion of the plurality of end users.